SQL*Loader error ORA-00600 and ORA-26095

Hi all,
We have a problem with the SQL*Loader Utility. We use an 8i-Database (8.1.7) and SQL*Loader 9.2.0.1.0. We have no Trims or other functions active in the control file and do a direct path load.
It used to work properly until this morning.
Now we have the following errors (it is in German - but I can translate it):
Satz 90153: Abgelehnt - Fehler in Tabelle SCHEMA1.T_IMPORT.
ORA-00600: Interner Fehlercode, Argumente: [klaprs_50], [7], [], [], [], [], [], []
... about 50 equal errors
Specify SKIP=90171 when continuing the load.
SQL*Loader-926: OCI-Fehler; uldlm:OCIDirPathFinish fÃ¼r Tabelle SCHEMA1.T_IMPORT
ORA-26095: Nicht verarbeitete Stream-Daten vorhanden
SQL*Loader-2026: Der Ladevorgang wurde abgebrochen, weil er nicht fortgesetzt werden kann.
Specify SKIP=90171 when continuing the load.
Trnaslation:
00600 - Internal error code, arguments: ...
OCI-Fehler = OCI error
fÃ¼r Tabelle = for table
ORA-26095: Nicht verarbeitete Stream-Daten vorhanden = Non processed stream data existing
SQL*Loader-2026: Der Ladevorgang wurde abgebrochen, weil er nicht fortgesetzt werden kann. = Load process has been cancelled as it cannot be continued.
Has anyone got a clue?!?!?!

Hi,
It's very clear that import 9i is for an import into 9i database.
Upgrade 8i to 9i indicates that we can make an export 8i from 8i database and import 9i into 9i database, but never use a tools like export from other version...
If you want import data from 9i database into 8i use exp tools 8i, and imp 8i.
I devise you to read Metalink note 132904.1 - compatibility matrix for export & import between different oracl version.
Nicolas.

Similar Messages

Difference between ora-00600 and ora-07445

Hi all,
Both ora-00600 and 07445 are generic errors, which arises due to n number of reasons. Is there any particular difference between these two errors. If so please let me know.....
Thanks in advance
kumareshan.......

I don't think the statement is true. The answers is in the two metalink doc you posted.
[Note:146580.1] Additional ORA-600 related information.
[Note:211909.1] Additional ORA-7445 related information.
in short,
ORA-600 is from kernel code of the Oracle
An ORA-7445 error is raised by an Oracle server process when it has received a fatal signal from the operating system.

ORA-00600 and ORA-07445

Hello I have this erros located into udump\log_file:
Fri May 30 04:13:57 2008
SMON: Parallel transaction recovery tried
Fri May 30 04:14:38 2008
Errors in file l:\oracle\admin\opera\bdump\opera_j006_5992.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_msqsub+23] [PC:0x1FEE80B] [ADDR:0x5B3F] [UNABLE_TO_READ] []
Fri May 30 04:14:42 2008
SMON: Parallel transaction recovery tried
Fri May 30 06:26:57 2008
Errors in file l:\oracle\admin\opera\udump\opera_ora_900.trc:
ORA-00600: internal error code, arguments: [kokcup:01], [0], [0], [], [], [], [], []
Fri May 30 06:26:58 2008
Errors in file l:\oracle\admin\opera\udump\opera_ora_900.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kksasd+16] [PC:0x86D4F0] [ADDR:0x458B03CB] [UNABLE_TO_READ] []
ORA-00600: internal error code, arguments: [kokcup:01], [0], [0], [], [], [], [], []
Fri May 30 06:26:59 2008
Errors in file l:\oracle\admin\opera\udump\opera_ora_900.trc:
ORA-00600: internal error code, arguments: [kssadpm: null parent], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kksasd+16] [PC:0x86D4F0] [ADDR:0x458B03CB] [UNABLE_TO_READ] []
ORA-00600: internal error code, arguments: [kokcup:01], [0], [0], [], [], [], [], []
Fri May 30 06:27:00 2008
Errors in file l:\oracle\admin\opera\udump\opera_ora_900.trc:
ORA-00600: internal error code, arguments: [kssadpm: null parent], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kksasd+16] [PC:0x86D4F0] [ADDR:0x458B03CB] [UNABLE_TO_READ] []
ORA-00600: internal error code, arguments: [kokcup:01], [0], [0], [], [], [], [], []
Fri May 30 07:00:38 2008
Thread 1 advanced to log sequence 5849
Current log# 9 seq# 5849 mem# 0: I:\ORACLE\ORADATA\OPERA\REDO9_01.RDO
Fri May 30 10:04:03 2008
Thread 1 cannot allocate new log, sequence 5850
Private strand flush not complete
Current log# 9 seq# 5849 mem# 0: I:\ORACLE\ORADATA\OPERA\REDO9_01.RDO
Thread 1 advanced to log sequence 5850
Current log# 10 seq# 5850 mem# 0: I:\ORACLE\ORADATA\OPERA\REDO10_01.RDO
Fri May 30 10:05:20 2008
ALTER DATABASE BACKUP CONTROLFILE TO 'C:\Program Files\OmniBack\tmp\ctrl_OPERA.dbf' REUSE
Fri May 30 10:05:20 2008
Completed: ALTER DATABASE BACKUP CONTROLFILE TO 'C:\Program Files\OmniBack\tmp\ctrl_OPERA.dbf' REUSE
I'm not so familiar with ORACLE. I have experience with MS SQL. Oracle create .trc files about 2KB each, 2GB every day.
I appreciate your help!
Message was edited by:
julata

Hi,
Thse both errors come under the category of internal errors.The best place to look for their troubleshooting and remedies is using Support Services.
Please look into metalink.oracle.com and search for these two error codes.
I would recommend to send teh trace to the Support and let a support guy handle it.
Aman....

SQL*LOADER ERROR 비교 (ORA-2359, ORA-1401)

제품 : ORACLE SERVER
작성날짜 : 2002-04-09
SQL*LOADER ERROR 비교 (ORA-2359, ORA-1401)
==========================================
PURPOSE
SQL*LOADER 를 사용하는 경우 ORA-2359 ERROR가 나는 경우와
ORA-1401 ERROR가 나는 경우를 비교한다.
Examples
table 의 desc가 다음과 같다고 가정하자.
SQL> create table test5(a varchar2(1000));
이 경우 delimiter 가 comma 인지 position 으로 구분되는지에 따라 error
message가 달리 나타난다.
1) ORA-2359 : field in datafile exceeded maximum specified length
load data
infile test.dat
replace
into table test5
fields terminated by ','
(a char) 로 실행 시 발생.
---> a char(1000) 으로 하면 error 해결이 가능하다.
2) ORA-1401: inserted value too large for column
load data
infile test.dat
replace
into table test5
fields terminated by ','
(a position(1:2000) char)
---> 이 경우 a position (1:1000) char 로 하면 해결 가능하다 .
* 참고로 + , - 기호와 comma 를 load 하기 위해서는 decimal external을
사용한다. (a position decimal external (10))
Reference Documents
---------------------

You hit Bug 3531336
Run the script catcio.sql from $ORACLE_HOME/rdbms/admin directory.
Run this in sys schema.
And then load the data with sqlloader.

Error ora-00600 and error-472

my database suddenly become unavilabe, I check the log file and i found error code ora-00600 and when i check the trace log file i found error error472. any suggest

Just search on metalink .. You can always use below note for trouble shooting 600/7445 errors ..
153788.1 - Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool

Ora 600 and ora 7445 error in oracle 10g r2

hi all,
we are using Oracle 10g r2.
os is windows 2003 server,
ram is 4 gb.
front end is java .
we got a below mentioned errors.
i got the RA-00600: internal error code, arguments: [qerghFetch:inc], [], [], [], [], [], [], [],
and ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x61F04AC9] [ADDR:0xC] [UNABLE_TO_READ] []
and Error 0 in kwqmnpartition(), aborting txn errors.
for aug 3 11.42.47 we got a ora 600 error after that through front end (java) users can't able to connect the database.the not able to executed the query session disconnected error.
what is reason for theis error . how it will rectifiy.?
pls advice.Below i attached the alret log message .
Sun Aug 02 04:04:24 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 05:48:10 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 05:49:10 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 07:38:49 2009
Thread 1 advanced to log sequence 1732
Current log# 3 seq# 1732 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
Sun Aug 02 07:44:14 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 07:45:14 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 22:00:26 2009
Thread 1 advanced to log sequence 1733
Current log# 1 seq# 1733 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG
Mon Aug 03 07:08:15 2009
Thread 1 advanced to log sequence 1734
Current log# 2 seq# 1734 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
Mon Aug 03 09:28:23 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 09:30:27 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 11:42:47 2009
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_6012.trc:
ORA-00600: internal error code, arguments: [qerghFetch:inc], [], [], [], [], [], [], []
Mon Aug 03 13:20:00 2009
Thread 1 advanced to log sequence 1735
Current log# 3 seq# 1735 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
Mon Aug 03 16:07:07 2009
Errors in file e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_4756.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x61F04AC9] [ADDR:0xC] [UNABLE_TO_READ] []
Mon Aug 03 16:07:11 2009
Process m000 died, see its trace file
Mon Aug 03 16:07:11 2009
ksvcreate: Process(m000) creation failed
Mon Aug 03 16:08:37 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 16:10:40 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 17:25:05 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 17:27:11 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 17:32:19 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 17:33:24 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 18:52:08 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 18:54:09 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 19:05:33 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 19:09:02 2009
Errors in file e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_5132.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7C34126B] [ADDR:0x0] [UNABLE_TO_WRITE] []
Mon Aug 03 19:10:27 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn

Hi reshumakur
As this is your PRODUCTION system THEN_ The best help to offer in case of ORA-600, and ORA-7445 is to open SR with metalink. Submit with the SR the following
1- Alert log
2- Trace files (in ur case e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_6012.trc: and e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_4756.trc:)
3- Describe what was happening when you had these errors.
Try to avoid free help when you have ORA-600 and ORA-07445. This errors could be becuase of BUGS. Oracle Support will know this from the call stack in the trace file.
Then Do your best to patch 10.2.0.4 and the latest CPU patch.
Good Luck

Error ORA-00604 AND ORA-00036

How to resolve ora error ORA-00604 and ORA-00036.
I am getting this error in alert.log:
ORA-00604: ERROR OCCURED AT RECURSIVE SQL LEVEL 51
ORA-00036: MAXIMUM NUMBER OF RECURSIVE SQL LEVELS (50) EXCEEDED.

Did someone create an 'after servererror' trigger?
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4018285967344
Read the part where he provides a query to find the trigger:
select owner, trigger_name
from dba_triggers
where trigger_type = 'AFTER EVENT';

Worker fails when running MSDODPCODE.sql causing ORA-33290 and ORA-06512

Hi All,
Hopefully somebody can help / point me in the right direction. I'm testing the process of upgrading our R12.0.5 Financials (Database 10.2.0.4) to R12.1.3 and have hit a problem when applying the 12.1.1 Maintenance Pack.
The worker has failed with the following in it's log file.
"sqlplus -s APPS/***** @/u01/app/applmgr/CGSYSTST/apps/apps_st/appl/msd/12.0.0/patch/115/sql/MSDODPCODE.sql
begin
ERROR at line 1:
ORA-33290: Analytic workspace ODPCODE cannot be attached in the mode you requested because another user has it attached in an incompatible mode.
ORA-06512: at "SYS.DBMS_AW", line 67
ORA-06512: at "SYS.DBMS_AW", line 131
ORA-06512: at "SYS.DBMS_AW", line 792
ORA-06512: at "SYS.DBMS_AW", line 767
ORA-06512: at "APPS.MSD_AW_LOADER", line 10
ORA-06512: at line 3"
It might be worth noting that I also hit the same problem when testing RUP 6 for R12.0.6 - it was partially because of this that I decided to scrap going to 12.0.6 1st and go straight to R12.1.3 - making it a much bigger upgrade.
Thanks
Andy

Hi Taher,
1st few lines from /u01/app/oracle/CGSYSTST/db/tech_st/10.2.0/admin/CGSYSTST_trinity/udump/cgsystst_ora_7942.trc are....
Dump file /u01/app/oracle/CGSYSTST/db/tech_st/10.2.0/admin/CGSYSTST_trinity/udump/cgsystst_ora_7942.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options ORACLE_HOME = /u01/app/oracle/CGSYSTST/db/tech_st/10.2.0
System name: Linux
Node name: TRINITY
Release: 2.6.16.60-0.39.3-smp
Version: #1 SMP Mon May 11 11:46:34 UTC 2009
Machine: x86_64
Instance name: CGSYSTST
Redo thread mounted by this instance: 1
Oracle process number: 17
Unix process pid: 7942, image: oracle@TRINITY
*** ACTION NAME:() 2011-03-07 12:07:03.718
*** MODULE NAME:(SQL*Plus) 2011-03-07 12:07:03.718
*** SERVICE NAME:(CGSYSTST) 2011-03-07 12:07:03.718
*** SESSION ID:(341.32826) 2011-03-07 12:07:03.718 Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x2af815d5ce17, PC: [0x2af713076608, intelfast_memcpy.A()+10]
*** 2011-03-07 12:07:03.718
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [_intel_fast_memcpy.A()+10] [SIGSEGV] [Address not mapped to object] [0x2AF815D5CE17] [] [] Current SQL statement for this session:
begin
-- attach code aw
msd_aw_loader.attach_code_aw;
-- create temp marker variable to prevent individual scripts from updating
dbms_aw.execute('define _noupdate session boolean'); end;
Andy

Ora - 01110 and ora 01157 error

Hi,
I am using linux 9i and solaris 5.8 .while i am connecting to the database it shows the ora - 01110 and ora 01157 error.i moved the temp datafile to some location after that only i receiced that error.then i moved the temp file to the particular location.after that what i can to do to resolve the error.
plz in detail sql query.
Thanks
gobi.

Can you detail how you are moving the file? Are you using one of the following methods:
With the database down
move/rename the file with OS commands
mount the database and issue the following
alter database rename file '<original path and file name>' to '<new path and file name>';
Open the database
or
With the database open take the tablespace the contains the files to be moved/rename offline.
move/rename the files with OS commands.
alter tablespace <tablespace name> rename datafile '<original path and file name>' to '<new path and file name>';
Bring the tablespace back online.

Work around/Alternate solution for Oracle error ORA-01460 and ORA-02063

After the installation of Oracle.DataAccess version 2.111.7.20, I get the following error.(the code worked fine with Oracle.DataAccess version 9.2.0.700 )
I have attached the error as well as the sample code.
ORA-01460 and ORA-02063 are known bugs in the new ODP but would like to know if there is any Work around/Alternate solution for this problem(other than
the use of stored procs)..
Thanks!
Error:
ORA-01460: unimplemented or unreasonable conversion requested
ORA-02063: preceding line from BSREAD_STAGINGRO at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck)
at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, Boolean bCheck)
at Oracle.DataAccess.Client.OracleCommand.ExecuteReader(Boolean requery, Boolean fillRequest, CommandBehavior behavior)
at Oracle.DataAccess.Client.OracleCommand.ExecuteReader()
SampleCode
private bool isValidFieldData(string clientName, string fieldNumber, string uniqueID, string clientID)
using (OracleConnection mBSConnection = new OracleConnection(mBSConnectionString))
OracleDataReader oRdr = null;
OracleCommand Valid_FieldData_Command = null;
try
Valid_FieldData_Command = new OracleCommand();
Valid_FieldData_Command.Connection = mBSConnection;
Valid_FieldData_Command.CommandText = "SELECT uniqueid FROM EXTDB.BSData WHERE agencyid = :agencyid and agencyname=:agencyname AND fieldnumber =:fieldnumber AND uniqueid = :uniqueid";
Valid_FieldData_Command.Parameters.Add(":agencyid", OracleDbType.Varchar2, 255).Value = agencyID;
Valid_FieldData_Command.Parameters.Add(":agencyname", OracleDbType.Varchar2, 255).Value = agencyName;
Valid_FieldData_Command.Parameters.Add(":fieldnumber", OracleDbType.Varchar2, 255).Value = fieldNumber;
Valid_FieldData_Command.Parameters.Add(":uniqueid", OracleDbType.Varchar2, 255).Value = uniqueID;
mBSConnection.Open();
oRdr = Valid_FieldData_Command.ExecuteReader(); ->Error occurs here
The error occurs whenever the length of any of the parameter is increased. But there is no specific length where it is breaking down.
For example in this case, it breaks down with the given error if
agencyID > 8
agencyName > 6
fieldNumber > 9
uniqueid > 6

The problem was mapping input parameter type.
VARCHAR2-type mapping input parameter works with String-type PF parameter. But CHAR-type won't.

ORA-00001 and ORA-06512 error on DBMS_WM.ResolveConflicts

We are getting unique constraint error in Production Database. We are able to merge most of the workspaces with no issues. One workspace is givign errors on merge.
Here is the code
begin
dbms_wm.gotoworkspace('denialletterspoc_onmzpulp');
dbms_wm.setdiffversions('denialletterspoc_onmzpulp','LIVE');
dbms_wm.SetConflictWorkspace('denialletterspoc_onmzpulp');
commit;
DBMS_WM.BeginResolve('denialletterspoc_onmzpulp');
DBMS_WM.ResolveConflicts(
workspace => 'denialletterspoc_onmzpulp',
table_name => 'MCM_MESSAGE',
where_clause => ' id in (8403026,10134822,8259485,8259488,8426289,8426287,10186643,8426288) ',
keep => 'CHILD'
exception when others then
DBMS_WM.RollbackResolve('denialletterspoc_onmzpulp');
raise;
end;
ORA-00001: unique constraint (T2.MCM_MESSAGE_PK) violated
ORA-06512: at line 16
I looked at the date in XXX_lt tables and it does not look suspecious. Please help us understand
ORA-00001 and ORA-06512 error.
Amit Gangwar

Hi, Ben
Our OWM_VERSION is 10.2.0.4.3.
I tried disable and enable constraint MCM_MESSAGE_PK. But didn't fix our issue.
Split where clause from " id in (...) " syntax to " id = ... " syntax will reduce performance heavily. And I did some test that " id in (...) " syntax works well in our dev env.
I opened our trace file and get below plsql block. When I perform it get same error with our original codes. Please notice the part of "forall wm_indx in WM_rowids.first .. WM_rowids.last execute immediate 'begin insert into T2.MCM_MESSAGE_lt ... ...", error occurred here. But if I change the "forall" syntax to normal " for ... loop" syntax then no error here. Can you give me some advice or suggestion?
DECLARE
WM_rowids wmsys.lt_ctx_pkg.rowidTabType;
WM_rowids_vt wmsys.lt_ctx_pkg.rowidTabType;
WM_curver wmsys.lt_ctx_pkg.int_tab;
WM_vtRow wmsys.lt_ctx_pkg.int_tab;
WM_nextver wmsys.lt_ctx_pkg.nextver_tab;
WM_found integer := 0;
BEGIN
dbms_wm.gotoworkspace('denialletterspoc_onmzpulp');
dbms_wm.setdiffversions('denialletterspoc_onmzpulp','LIVE');
dbms_wm.SetConflictWorkspace('denialletterspoc_onmzpulp');
/* update the auxilliary table of snapshots */
/* These are rows in the current version that have already been resolved once */
update T2.MCM_MESSAGE_aux st
set (snapShotChild, snapShotParent, versionParent) =
(select p.WM_childds, p.WM_parentds, p.WM_parentver
from T2.MCM_MESSAGE_pkc p
where p.ID = st.ID),
value = '0',
wm_opcode = 'CC'
where st.versionChild = 614
and (ID) in (select ID
from T2.MCM_MESSAGE_pkc p
where (id in (8403026,
10134822,
8259485,
8259488,
8426289,
8426287,
10186643,
8426288)));
select distinct WM_ridchild bulk collect
into WM_rowids
from T2.MCM_MESSAGE_pkc
where (id in (8403026,
10134822,
8259485,
8259488,
8426289,
8426287,
10186643,
8426288))
and WM_childver != 614;
if (WM_rowids.first is not null) then
WM_found := 1;
forall wm_indx in WM_rowids.first .. WM_rowids.last
update T2.MCM_MESSAGE_lt
set retireTime = wmsys.owm_9ip_pkg.activeTimeForDML,
nextver = wmsys.lt_ctx_pkg.getNextVer(nextver,
614,
version,
'denialletterspoc_onmzpulp',
'CRS_LEAF',
22)
where rowid = WM_rowids(wm_indx)
returning wmsys.lt_ctx_pkg.getCurNextVer bulk collect into WM_nextver;
/* These are the rows that have not yet been resolved after the latest BeginResolve */
forall wm_indx in WM_rowids.first .. WM_rowids.last execute immediate
'begin insert into T2.MCM_MESSAGE_lt(ID,DPS_APPLICATION_ID,TYPE_ID,NAME,PRIVILEGED,CAMPAIGN_ID,TEXT,FILE_NAME,GRAPHIC_WIDTH,GRAPHIC_HEIGHT,DESCRIPTION,ACTIVE,INCLUDE_IN_LIBRARY,MESSAGE_FILTER_ID,OP_USER_ID,OP_WORKSPACE,OP_TIME,version,createtime,retiretime,nextver,delstatus,ltlock)
(select t1.ID,t1.DPS_APPLICATION_ID,t1.TYPE_ID,t1.NAME,t1.PRIVILEGED,t1.CAMPAIGN_ID,t1.TEXT,t1.FILE_NAME,t1.GRAPHIC_WIDTH,t1.GRAPHIC_HEIGHT,t1.DESCRIPTION,t1.ACTIVE,t1.INCLUDE_IN_LIBRARY,t1.MESSAGE_FILTER_ID,t1.OP_USER_ID,t1.OP_WORKSPACE,t1.OP_TIME,614, wmsys.owm_9ip_pkg.activeTimeForDML, null,:1, sign(delstatus)*(abs(delstatus)+1),
wmsys.lt_ctx_pkg.checkngetlock(''C'', t1.ltlock, t1.nextver, ''denialletterspoc_onmzpulp'', 0,
''MODIFY'', t1.version, t1.delstatus, 0, 1)
from T2.MCM_MESSAGE_lt t1
where t1.rowid = :2); end;'
using WM_nextver(wm_indx),
WM_rowids(wm_indx)
end if;
if (WM_found = 1) then
wmsys.lt_ctx_pkg.update_modified_tables('T2',
'MCM_MESSAGE',
614,
'denialletterspoc_onmzpulp',
22);
end if;
if (WM_found = 1) then
forall wm_indx in WM_rowids.first .. WM_rowids.last
delete from T2.MCM_MESSAGE_aux
where (ID) in (select ID
from T2.MCM_MESSAGE_lt
where rowid = WM_rowids(wm_indx))
and childState = 'denialletterspoc_onmzpulp';
end if;
/* now insert new syncing information about these rows */
execute immediate 'insert into T2.MCM_MESSAGE_aux (
select ID,
p.WM_childstate, p.WM_parentstate,
p.WM_childds, 614, p.WM_parentds, p.WM_parentver, ''0'',''CC''
from T2.MCM_MESSAGE_pkc p
where ( id in (8403026,10134822,8259485,8259488,8426289,8426287,10186643,8426288) ) )';
END;
Thanks
Amos

ORA-01401 and ORA-12899 : "too large for column" error messages

I posted this already in the Database - General forum.
Sorry for the double post.
For the past 8hours, I have been googling about
the related ORA-01401 and ORA-12899 error
messages.
I noticed that ORA-01401 had been removed from the list
of error messages in Oracle 10g documentation.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e900.htm#sthref30
And, ORA-12899 has been added.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e12700.htm
1. Is there an official Oracle document (e.g. release notes) stating such facts? If so, please provide the link.
2. Why did Oracle change the error code and not just update ORA-01401?
3. Someone posted in http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:7143933880166
Even if installed Oracle is 10g, when he tried to "insert a 100 into a number(2).",
he supposedly got ORA-01401. So, is ORA-01401 still part of 10g or not?
I have yet to confirm this myself.
Sorry for being meticulous. Our customer just wants to know the
information for the 2nd question. It's hard to convince them without
showing official documents.
Thanks!

1)
Well, go to Metalink and check out Note 119119.1 (B.4) and Note:287754.1
2)
Such details are seldom published. One guess is what they changed altered the reason behind the message so using the same code would be a bad idea.
3)
If you are referring to the occurrence of ora-1401 from a select on a XE db, that may be a bug.

ORA-01180 and ORA-01110 error when restoring database by RMAN in 11.1.0.6.0

I have a new installed database running in ARCIHVELOG mode on SUSE 10SP3. Catalog is not used. When I try to restore the database from a level 0 backup based on SCN, ORA-01180 and ORA-01110 were raised out today. Please help me through this. Thx. The senario follows:
1. I got the current SCN by "select dbms_flashback.get_system_change_number from dual". Say it's 12345;
2. I did a level 0 hot backup with current control file, archived logs and parameter files. Everything went well;
3. Some other DMLs are applied to the database;
4. I want to do a SCN-based incomplete recovery for this database to SCN 12345. Then I
1) shutdown immediate;
2) startup nomount;
3) restore the control file from backupset;
5) startup mount;
6) catalog start with "[backupset path]";
7) restore database until scn 12345.
Just at step 4.7, ORA-01180 and ORA-01110 were raised out, saying cannot create data file 1. Note: Backup files are existing and file permissions are all OK.
Then I issues "list incarnation of database". There is just one record with incarnation id 1.
So I queried v$log_history, found serveral record there. The most recent one has NEXT_SCN later than 12345, say 12400. Then I tried to restore database until this SCN. It WORKED! The restore and recovery succeeded.
My questions are:
1. Why cannot I restore the database to a previous SCN, say 12345, but 12400 is OK?.
2. If the database was RESETLOG prior to my recovery, should I reset database to the incarnation where I took my backup? What can I do if there is no that incarnation information in my control file?
Waiting for your suggestion.

Hi guys. There is one update.
This issue is caused by the incorrect SCN vs. backup set. I got this SCN before the backup started. According to Oracle docs, it's not allowed for an SCN based recovery.
Now, I changed the sequence of my operations, so that SCN is got once backup is done, which is exact the "most recent sequence# and least SCN" mentioned by some thread in this forum. It works now.
Anyone could explain why the SCN got prior to the level 0 backup is not recognized by restore/recovery phase? Thanks.

SQL Loader Error using regexp_replace

Hi Guys,
i am trying to using sql loader to load data and one column in control file is
x1 POSITION(718:725) DATE "YYYYMMDD" NULLIF FI_CLM_RCPT_DT = BLANKS,
XYZ POSITION(736:745) CHAR "regexp_replace(substr(:XYZ,1,9),\'[^1|Y|N|U|W]\',\' \')||regexp_replace(substr(:XYZ,10,1),\'[^Z]\', \' \'))")
But at last part i am getting error
SQL*Loader-951: Error calling once/load initialization
ORA-02373: Error parsing insert statement for table TDESAI_DBA.HAJI_CLM_A.
ORA-00933: SQL command not properly ended
I know the error is with XYZ Column but where. Or am i doing something wrong?
Can you guys help me

Please see the discussion on the Semantic Technologies OTN form at SQL*Loader error 350 using SDO_RDF_TRIPLE_S constructor

ORA-604 and ORA-4031 during installation of SAP

Hi,
I tried to install Oracle 10.2.0.2 on Windows 2003 with SAP R3E 47X2.
However, during the installation on the Database Load phases it pops up a ORA-604 and ORA-4031 error log. It was unable to completed the Database Load phase showed as R3 load jobs: running 1, waiting 0.
I tried to set the share pool in init.ora as shared_pool_size = 40000000. It still show up as shared memory issue.
The log shows as,
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: START OF LOG: 20081201110818
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: version R6.40/V1.4 [UNICODE]
Compiled Dec 15 2005 22:22:21
E:\usr\sap\IDE\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAPSSEXC.cmd -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAPSSEXC.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
DbSl Trace: Failed to register client info: orc=604
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=15)
(DB) ERROR: DDL statement failed
(TRUNCATE TABLE "DYNPSOURCE")
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4120 bytes of shared memory ("shared pool","select user#,type# from user...","Typecheck","kgghteInit")
(DB) INFO: disconnected from DB
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: job finished with 1 error(s)
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: END OF LOG: 20081201110858
Could anyone help me about it?
Thanks.

hi Nikhuj,
I reset the installation and however endup the installation still have an error. Please help me to check with the following:
SQL> connect system
Enter password:
ERROR:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4120 bytes of shared memory ("shared
pool","select ts#,file#,block#,nvl(...","Typecheck","kgghtInit")
SQL> show parameters shared_pool;
NAME                   TYPE     VALUE
shared_pool_reserved_size   big integer 12881756
shared_pool_size         big integer 124M
SQL> alter system set shared_pool_size=40000000;
alter system set shared_pool_size=40000000
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-04034: unable to shrink pool to specified size
As I had changed the parameter in initsmpl.ora shared pool from 10000000 to 40000000. The log as below was showing that:
SAPAPPL1.log:
Error accessing package DBMS_APPLICATION_INFO
Connected.
(IMP) INFO: import of LXE_PPX__1 completed (1 rows) #20081201200124
(DB) INFO: LXE_PPX__1~0 created #20081201200124
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=34)
(DB) ERROR: DDL statement failed
(CREATE INDEX "LXE_PPX__1~CNT" ON "LXE_PPX__1" ( "T_LANG" , "S_LANG" ,
"DOMATYP" , "DOMANAM" , "USAGECNT" ) TABLESPACE PSAPIDE STORAGE (INITIAL 0 NEXT
0000010240K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4120 bytes of shared memory ("shared pool","CREATE
UNIQUE INDEX "PA0399~...","Typecheck","kgghteInit")
(DB) INFO: disconnected from DB
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: job finished with 1 error(s)
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: END OF LOG: 20081201200129
SAPAPPL2.log:
(DB) INFO: TCN2T~0 created #20081201200843
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE TABLE "TCN41" ( "MANDT" VARCHAR2(9) DEFAULT '000' NOT NULL , "PLNAW"
VARCHAR2(3) DEFAULT ' ' NOT NULL , "PROFIDNETZ" VARCHAR2(21) DEFAULT ' ' NOT NULL
, "FLG_ERF_H" VARCHAR2(3) DEFAULT ' ' NOT NULL , "ESOKZ" VARCHAR2(3) DEFAULT ' '
NOT NULL , "EKORG" VARCHAR2(12) DEFAULT ' ' NOT NULL , "KSTAR_FRMD" VARCHAR2(30)
DEFAULT ' ' NOT NULL , "STEUS_WORK" VARCHAR2(12) DEFAULT ' ' NOT NULL ,
"STEUS_FRMD" VARCHAR2(12) DEFAULT ' ' NOT NULL , "STEUS_PRIM" VARCHAR2(12)
DEFAULT ' ' NOT NULL , "KSTAR_COST" VARCHAR2(30) DEFAULT ' ' NOT NULL ,
"KSTAR_SERV" VARCHAR2(30) DEFAULT ' ' NOT NULL , "STEUS_SERV" VARCHAR2(12)
DEFAULT ' ' NOT NULL , "DAUNE" VARCHAR2(9) DEFAULT ' ' NOT NULL , "ARBEH"
VARCHAR2(9) DEFAULT ' ' NOT NULL , "WAERS" VARCHAR2(15) DEFAULT ' ' NOT NULL ,
"SLWID" VARCHAR2(21) DEFAULT ' ' NOT NULL , "LVARI" VARCHAR2(6) DEFAULT ' ' NOT
NULL , "INDET" VARCHAR2(3) DEFAULT ' ' NOT NULL , "BUKRS" VARCHAR2(12) DEFAULT '
' NOT NULL , "AOB_KEY" VARCHAR2(3) DEFAULT ' ' NOT NULL , "VORNR_DEL" VARCHAR2
(12) DEFAULT ' ' NOT NULL , "TERKZ" VARCHAR2(3) DEFAULT ' ' NOT NULL , "AUART"
VARCHAR2(12) DEFAULT ' ' NOT NULL , "WERKS" VARCHAR2(12) DEFAULT ' ' NOT NULL ,
"DISPO" VARCHAR2(9) DEFAULT ' ' NOT NULL , "RSCHL_OFER" VARCHAR2(18) DEFAULT ' '
NOT NULL , "RSCHL_OFRD" VARCHAR2(18) DEFAULT ' ' NOT NULL , "RSCHL_UFER"
VARCHAR2(18) DEFAULT ' ' NOT NULL , "RSCHL_UFRD" VARCHAR2(18) DEFAULT ' ' NOT
NULL , "RSCHL_OCST" VARCHAR2(18) DEFAULT ' ' NOT NULL , "RSCHL_UCST" VARCHAR2(18)
DEFAULT ' ' NOT NULL , "GR_PRF_GR" VARCHAR2(12) DEFAULT ' ' NOT NULL ,
"GR_PRF_NAM" VARCHAR2(36) DEFAULT ' ' NOT NULL , "FHORI" VARCHAR2(9) DEFAULT ' '
NOT NULL , "NETSTUFE" VARCHAR2(6) DEFAULT '00' NOT NULL , "VAGRP" VARCHAR2(9)
DEFAULT ' ' NOT NULL , "MSGTY" VARCHAR2(3) DEFAULT ' ' NOT NULL , "AOB_DARST"
VARCHAR2(3) DEFAULT ' ' NOT NULL , "VRG_DARST" VARCHAR2(3) DEFAULT ' ' NOT NULL ,
"NO_DISP" VARCHAR2(3) DEFAULT ' ' NOT NULL , "COLKZ_ELEM" VARCHAR2(33) DEFAULT '
' NOT NULL , "COLKZ_TEIL" VARCHAR2(33) DEFAULT ' ' NOT NULL , "COLKZ_MLST"
VARCHAR2(33) DEFAULT ' ' NOT NULL , "COLKZ_DOKU" VARCHAR2(33) DEFAULT ' ' NOT
NULL , "COLKZ_MAT" VARCHAR2(33) DEFAULT ' ' NOT NULL , "VSPRF" VARCHAR2(21)
DEFAULT ' ' NOT NULL , "CLASF" VARCHAR2(3) DEFAULT ' ' NOT NULL , "PROFILE_ID"
VARCHAR2(30) DEFAULT ' ' NOT NULL , "BALK_PROF" VARCHAR2(36) DEFAULT ' ' NOT NULL
, "KBED" VARCHAR2(3) DEFAULT ' ' NOT NULL , "KKALKR" VARCHAR2(3) DEFAULT ' ' NOT
NULL , "LSTVAR" VARCHAR2(36) DEFAULT ' ' NOT NULL , "MATKL" VARCHAR2(27) DEFAULT
' ' NOT NULL , "MATEXIT" VARCHAR2(3) DEFAULT ' ' NOT NULL , "EKGRP" VARCHAR2(9)
DEFAULT ' ' NOT NULL , "MATKL_FRMD" VARCHAR2(27) DEFAULT ' ' NOT NULL ,
"EKGRP_FRMD" VARCHAR2(9) DEFAULT ' ' NOT NULL , "POSNR_MAT" VARCHAR2(12) DEFAULT
'0000' NOT NULL , "SCHED_END" VARCHAR2(3) DEFAULT ' ' NOT NULL , "SCEND_ACT"
VARCHAR2(3) DEFAULT ' ' NOT NULL , "NT_SEARCH1" VARCHAR2(6) DEFAULT ' ' NOT NULL
, "NT_SEARCH2" VARCHAR2(6) DEFAULT ' ' NOT NULL , "NT_SEARCH3" VARCHAR2(6)
DEFAULT ' ' NOT NULL , "MFLIC" VARCHAR2(9) DEFAULT ' ' NOT NULL , "MEINH_FRMD"
VARCHAR2(9) DEFAULT ' ' NOT NULL , "MEINH_SERV" VARCHAR2(9) DEFAULT ' ' NOT NULL
, "KSTAR_MATVORPL" VARCHAR2(30) DEFAULT ' ' NOT NULL , "KZERB" VARCHAR2(3)
DEFAULT ' ' NOT NULL , "VALID" VARCHAR2(21) DEFAULT ' ' NOT NULL , "VALID_VG"
VARCHAR2(21) DEFAULT ' ' NOT NULL , "SUBST" VARCHAR2(21) DEFAULT ' ' NOT NULL ,
"SUBST_VG" VARCHAR2(21) DEFAULT ' ' NOT NULL , "FPART" VARCHAR2(6) DEFAULT ' '
NOT NULL ) TABLESPACE PSAPIDE STORAGE (INITIAL 65536 NEXT 0000000040K MINEXTENTS
0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4040 bytes of shared memory ("shared pool","select
i.obj#,i.ts#,i.file#,...","Typecheck","seg:kggfaAllocSeg")
(DB) INFO: disconnected from DB
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: job finished with 1 error(s)
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: END OF LOG: 20081201200843
SAPAPPL0.log:
(DB) INFO: PA0398~0 created #20081201200124
(DB) INFO: PA0399 created #20081201200124
(IMP) INFO: import of PA0399 completed (12 rows) #20081201200124
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-4031 occurred when executing SQL statement (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "PA0399~0" ON "PA0399" ( "MANDT", "PERNR", "SUBTY",
"OBJPS", "SPRPS", "ENDDA", "BEGDA", "SEQNR" ) TABLESPACE PSAPIDE STORAGE (INITIAL
0 NEXT 0000000080K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 4031)
error message returned by DbSl:
ORA-04031: unable to allocate 4120 bytes of shared memory ("shared pool","CREATE
UNIQUE INDEX "PA0399~...","Typecheck","kgghteInit")
(DB) INFO: disconnected from DB
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: job finished with 1 error(s)
E:\usr\sap\IDE\SYS\exe\run/R3load.exe: END OF LOG: 20081201200129

SQL*Loader error ORA-00600 and ORA-26095

Similar Messages

Maybe you are looking for