ORA-16038: log string sequence# string cannot be archived
Answers were Sorted based on User's Feedback
Answer / geraldo viana
Verify in the LOG_ARCHIVE_DEST the variable FILE SYSTEM.
In almost cases the size of the file system is full.
Is This Answer Correct ? | 5 Yes | 1 No |
Answer / sandeep joel dmello
increase db_recovery_file_dest_size.
alter system set db_recovery_file_dest_size=4096M
scope=both;
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / kirankumar.upadhyayula
ORA-16038: log 2 string sequence# 48string cannot be
archived?
Ans:-alter system set db_recovery_file_dest_size=4096M
scope=both;
Is This Answer Correct ? | 0 Yes | 1 No |
Answer / guest
Cause: An attempt was made to archive the named file, but
the file could not be archived. Examine the secondary error
messages to determine the cause of the error.
Action: No action is required.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 3 No |
ORA-06521: PL/SQL: Error mapping function
ORA-08002: sequence string.CURRVAL is not yet defined in this session
ORA-26513: push error: master proc. string$RP.string failed for trans:string seq:string
ORA-31411: change set string is referenced by a change table
ORA-13769: Snapshots string and string do not exist.
ORA-32405: cannot alter tablespace for existing materialized view log
ORA-16095: Dependent destination removal for inactivation
ORA-01346: Dependent LogMiner sessions relying on supplementally logged data exist
PLS-00732: Illegal overload of ellipsis in formal parameter list
SQL*Loader-00554: error opening file
ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
ORA-33218: (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places.