java.sql.SQLException: ORA-00257: archiver error. Connect internal only, until freed
<BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@1a589ce1 threw exception: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDisabledException: Pool oimOperationsDB is Suspended, cannot allocate resources to applications..
When you are getting this kind of error and in nay of the managed servers then you need to check the database for the archivelog isssue
basically the archive error occurs when the archive-log destination getting filled and no space left on the device
connect to database and check the archivelog location and check the status of the db_recovery_file_dest size and Clear the arcchivelog's and configure the rman re-dentition policy according the environment and backup policy
In the alert log file you can see the message of the space issue and we need to delete some of the archive log's or if you have enough space left in the device you can add the db_recover_file_dest_size by using the alter system set command
************************************************************************
ARC2: Error 19809 Creating archive log file to '/u01/app/oracle/oracle/fast_recovery_area/OIASM/archivelog/2012_09_14/o1_mf_1_43_%u_.arc'
Fri Sep 14 19:18:26 2012
Errors in file /u01/app/oracle/oracle/diag/rdbms/oiasm/OIASM/trace/OIASM_arc3_5064.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 42949672960 bytes is 99.98% used, and has 9814016 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
Connect the rman and delete the archive log completed before 10 days
RMAN> delete noprompt archivelog all completed before 'sysdate -10';
Check the space in the
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
-------------------- ------------------ ------------------------- ---------------
CONTROL FILE 0 0 0
REDO LOG 0 0 0
ARCHIVED LOG 13.6 0 3
BACKUP PIECE 3.92 .02 3
IMAGE COPY 0 0 0
FLASHBACK LOG 0 0 0
FOREIGN ARCHIVED LOG 0 0 0
SQL> select * from V$RECOVERY_FILE_DEST;
NAME SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
-------------------- ----------- ---------- ----------------- ---------------
/u01/app/oracle/orac 4.2950E+10 7526307840 9814016 6
le/fast_recovery_are
a
Restart the managed servers connected to particular database now the servers state will be changed to the running mode ...when even the application which is deployed in the managed server goes down or nay connectivity problem between the database and the managed server then the server's state will be changed to the admin mode...............
No comments:
Post a Comment