moamaria
asked on
ORA-03113 ORA-24324 and when trying to export queue table.
When performing an ordinary full database export, I get the following errors:
EXP-00056: ORACLE error 3113 encountered
ORA-03113: end-of-file on communication channel
EXP-00056: ORACLE error 24324 encountered
ORA-24324: service handle not initialized
EXP-00056: ORACLE error 24324 encountered
ORA-24324: service handle not initialized
EXP-00056: ORACLE error 24324 encountered
ORA-24324: service handle not initialized
EXP-00056: ORACLE error 24324 encountered
ORA-24324: service handle not initialized
EXP-00000: Export terminated unsuccessfully
The thing is that the errors occur when trying to export a queue table created previosly.
It was created by the normal schema user, the same user that performs the export.
Any idea what to do?
EXP-00056: ORACLE error 3113 encountered
ORA-03113: end-of-file on communication channel
EXP-00056: ORACLE error 24324 encountered
ORA-24324: service handle not initialized
EXP-00056: ORACLE error 24324 encountered
ORA-24324: service handle not initialized
EXP-00056: ORACLE error 24324 encountered
ORA-24324: service handle not initialized
EXP-00056: ORACLE error 24324 encountered
ORA-24324: service handle not initialized
EXP-00000: Export terminated unsuccessfully
The thing is that the errors occur when trying to export a queue table created previosly.
It was created by the normal schema user, the same user that performs the export.
Any idea what to do?
This sort of errors leads to compilation problems. Very often on Linux/Unix installations after installing new products you will got these messages. the reason are changes in the kernel. In linux try to reinstall the old glibc library, in Windows look if the Oracle bin is the first in the path environment variable.
I would verify your environment setup ... env vars, permissions, etc.
ASKER
The misstake was that I've created the queue table using the wrong oracle client, i.e. another client than the one performing the export. Dropping the queue table and recreating it with the right client solved the problem
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It doesn't provide any solution....
It does
The misstake was that I've created the queue table using the wrong oracle client, i.e. another client than the one performing the export. Dropping the queue table and recreating it with the right client solved the problem
The misstake was that I've created the queue table using the wrong oracle client, i.e. another client than the one performing the export. Dropping the queue table and recreating it with the right client solved the problem