One option I can think of.
When you create the new database set your compatible parameter to 8.1.7.
Make use of the package to import the data. Disadvantage to this is you
cannot use some new features that require higher compatibility.

We used the above setup to avoid issues with our routines for a long time,
we just recently moved the compatible to a higher value, once we had all our
databases migrated to 9i.

If ORA-600 [qctstc2o1] is encountered, this would be due to bug
2170925/1805096. The compatibility parameter should also be set to a lower
version supporting long character, i.e. 8.1.7. Immediate workaround would be
to create copy of the remote table in a separate table with varchar2/clob
option.


Thanks!
amar kumar padhi
Oracle DBA/iDev



-----Original Message-----
From: G Nageswararao (GE Consumer Finance consultant)
[mailto:oracledba-ezmlmshield-x35670868.[Email address protected]
Sent: 16 June 2005 22:15
To: LazyDBA Discussion
Subject: Inserting data in LONG column over DB link from Oracle 9.2.0.6 to
Oracle 8.1.7.4


Hi,

Can any one help us to resolve this issue.

We are trying to insert data in a table which is having LONG data type from
Oracle 9.2.0.6 to Oracle 8.1.7.4 in a procedure.

When we try to compile the above procedure we are getting the following
error message:

PL/SQL: ORA-00600: internal error code, arguments: [qctstc2o1], [1], [0],
[178], [8], [0], [0], []

The same procedure is working fine if both databases are on Oracle 8.1.7.4.
Now we are upgrading one of the database and facing this problem.

Thanks and Regards,
Nageswara Rao



--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html

Oracle LazyDBA home page