This error should have been reported already at the time of installation.
Relinking will report again this error..? Java has been reinstalled. It is a good practice to relink at this juncture as we have been adviced.
Anyhow to take a chance I am relinking the Oracle S/w........
And time of Enabling the JVM This error was not reported.
I am little doubt here......
I have enabled the JVM (which i mean enabling java in database) in oracle database. Why Should I reliank oracle Software.
and I will elaborate problems little more:
When I will restart the database and then run the utlrp and export backup. For the first time it goes fine. But the if I re-run the same again... it will start giving the above mentioned errors. This will then Continue till I restart the database again......
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
EXP-00008: ORACLE error 3113 encountered
ORA-03113: end-of-file on communication channel
EXP-00000: Export terminated unsuccessfully
in In alert log, it reports ORA-7445 ...............