java.sql.SQLException: ORA-00257: archiver error. Connect internal only

[Former Member]

Hi All,

We are facing a strange issue with the ORACLE ARCHIVE files since a week and the below error we got it from defaulttrace file on central instace.

[EXCEPTION]

#6#257#64000#ORA-00257: archiver error. Connect internal only, until freed.

#jdbc:oracle:thin:@<HOSTNAME>:1527:PP0#<null>#java.sql.SQLException: ORA-00257: archiver error. Connect internal only, until freed.

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)

at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:293)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:357)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)

at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.getConnectionInternal(DBConnectionPool.java:193)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.getConnection(DBConnectionPool.java:135)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:75)

at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.getDataFromDB(CachedConfiguration.java:171)

at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.prepareRead(CachedConfiguration.java:241)

at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getData(ReadAccessConfiguration.java:92)

at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfiguration.java:848)

at com.sap.sldserv.DataCollector.getLastCollectTimeIntervalDatabase(DataCollector.java:763)

at com.sap.sldserv.DataCollector.checkTimeBasedRunDatabase(DataCollector.java:745)

at com.sap.sldserv.DataCollector.checkTimeBasedRun(DataCollector.java:736)

at com.sap.sldserv.DataCollector.check(DataCollector.java:360)

at com.sap.engine.services.timeout.TimeoutNode.check(TimeoutNode.java:97)

at com.sap.engine.services.timeout.TimeoutManagerImpl.multiThreadRun(TimeoutManagerImpl.java:489)

at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:20)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

2) #1.5 #D27E2001A00300580000000A001A60FE000451EB1D1937D3#1215970154198#com.sap.engine.core.thread.impl5.SingleThread##com.sap.engine.core.thread.impl5.SingleThread.SingleThread.execute().RuntimeException######364f80a0510111dd9deed27e2001a003#SAPEngine_System_Thread[impl:5]_112##0#0#Error##Plain###java.lang.IllegalArgumentException: Listener already registered !#

#1.5 #D27E2001A00300580000000B001A60FE000451EB1D193847#1215970154199#com.sap.engine.core.thread.impl5.SingleThread##com.sap.engine.core.thread.impl5.SingleThread.SingleThread.execute().RuntimeException######364f80a0510111dd9deed27e2001a003#SAPEngine_System_Thread[impl:5]_112##0#0#Error##Plain###java.lang.IllegalArgumentException: Listener already registered !

at com.sap.engine.services.timeout.TimeoutManagerImpl.register(TimeoutManagerImpl.java:189)

at com.sap.engine.services.timeout.TimeoutManagerImpl.registerTimeoutListener(TimeoutManagerImpl.java:148)

at com.sap.jms.server.destinationcontainer.service.impl.CleanUpServiceImpl.registerTimeOut(CleanUpServiceImpl.java:391)

at com.sap.jms.server.destinationcontainer.service.impl.CleanUpServiceImpl.resume(CleanUpServiceImpl.java:382)

at com.sap.jms.server.destinationcontainer.service.impl.CleanUpServiceImpl.timeout(CleanUpServiceImpl.java:216)

at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

The file system for the oraarch is /oracle/PP0/oraarch , we can see the same error continuosly in the log files if we there is a free space in /oracle/PP0/oraarch, but the same folder is filling 100% on sundays we are getting JAVA IVEW RUNTIME ERROR.

Any help is appreciated.

FYI. I'm just going thru the SAP Note 391 but not finding much info.

We are on AIX 5.3 , portal 7.0 , oracle 10g

Points will be awarded .

Regards,

Sreedhar Gunda

[stefan_koehler · Accepted solution]

Hello Sreedhar,

just for your information: http://ora-00257.ora-code.com/

> The file system for the oraarch is /oracle/PP0/oraarch , we can see the same error continuosly in the log files if we there is a free space in /oracle/PP0/oraarch, but the same folder is filling 100% on sundays we are getting JAVA IVEW RUNTIME ERROR.

How many free space is there if you see the ORA-00257 and how big are the redolog files?

Have you "only" one archive log destination (to /oracle/PP0/oraarch)?

Can you please post the spfile / pfile of your oracle database.

You will receive this error, if oracle can not archive the whole redolog file.

Regards

Stefan

[Former Member]

Resolved the issue