catpatch.sql has more to do with upgrade/migrate then patch sets, right!? I remember the old days when migrate meant 7 to 8...version change. upgrade meant 7.2 to 7.3...release change. and patch meant 8.0.4 to 8.0.5...patch set change. With out the help of the marketing dept. Oracle has totally hammered these meanings. I have a anther doc the explains where each term means to each version...but I got to hard to keep up. Now I just worry about it at the time...when planning for change. From my old notes; ----- Oracle Versions & Releases ----- The instructions in this document describe moving between different versions and releases of Oracle. Describes what each part of a release number represents. Example of an Oracle Release Number The release number 8.1.5.1.2 is displayed. The significance of each number (reading from left to right) is shown in the following table: Number Significance 8 Version number 1 New features release number 5 Maintenance release number 1 Generic patch set number 2 Platform specific patch set number Chris Marquez Oracle DBA -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of Michael McMullen Sent: Wed 10/5/2005 10:17 AM To: chiragdba@xxxxxxxxx Cc: Oracle-L Freelists Subject: Re: Export Problem I had a similar problem with export with my 9i databases. I installed the base software, then did the patches to current release (this was 9.2.0.4 i think). then created my database from scripts. I then got problems with my exports. Opened a tar with oracle, they said I had to startup migrate, then run catpatch.sql. Seemed like alot of hooey to me. But I did it and the problem went away and now I'll probably end up creating databases this way until I die. ----- Original Message ----- From: Chirag DBA To: Marquez, Chris Cc: Oracle-L Freelists Sent: Wednesday, October 05, 2005 9:58 AM Subject: Re: Export Problem Yes, I am already looking on google and metalink. but generally you need to run catpatch.sql when you upgrade yr DB, I mean apply the patch. but here we havent applied any patch. I run the catalog.sql, but same error for export. so now going to run catpatch.sql. regards - chirag On 10/5/05, Marquez, Chris <cmarquez@xxxxxxxxxxxxxxxx> wrote: ||is it safe to run catpatch.sql ? >>"upgraded yr DB and run catpatch.sql." ||we hanvent upgraded out DB I think you answered you own question. Safe maybe, maybe not...logical no. ||"for parameter NAME in function SET_TRANSFORM_PARAM" This seems suspicious...you looked more into this info? Chris Marquez Oracle DBA -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of Chirag DBA Sent: Wed 10/5/2005 9:38 AM To: Oracle-L Freelists Subject: Export Problem I am getting this error while exporting. METALNK says that you haverecently upgraded yr DB and run catpatch.sql. we hanvent upgraded out DB, is it safe to run catpatch.sql ? About to export specified users ... exporting pre-schema procedural objects and actions exporting foreign function library names for user SYSADM exporting PUBLIC type synonyms exporting private type synonyms exporting object type definitions for user SYSADM About to export SYSADM's objects ... exporting database links exporting sequence numbers exporting cluster definitions EXP-00056: ORACLE error 31600 encountered ORA-31600: invalid input value EMIT_SCHEMA for parameter NAME in function SET_TRANSFORM_PARAM ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105 ORA-06512: at "SYS.DBMS_METADATA_INT", line 3926 ORA-06512: at "SYS.DBMS_METADATA_INT", line 4050 ORA-06512: at "SYS.DBMS_METADATA", line 836 ORA-06512: at line 1 EXP-00000: Export terminated unsuccessfully -- //www.freelists.org/webpage/oracle-l