ORA-15451: missing or invalid volume size specifier
Cause:
The volume size specified was invalid.
Action:
Specify a valid volume size.
ORA-15452: missing or invalid stripe width
specifier
Cause:
The volume stripe width specified was invalid.
Action:
Specify a valid volume stripe width.
ORA-15453: invalid STRIPE_COLUMNS specifier
Cause:
An ADD VOLUME command did not specify a valid number of stripe columns.
Action:
Specify a valid number of stripe columns.
ORA-15454: ALTER DISKGROUP ALL cannot use single
volume names
Cause:
An ALTER DISKGROUP ALL command specified a single volume or a list of volumes
Action:
Use the ALL keyword when specifying volumes on multiple diskgroups.
ORA-15455: FORCE option cannot be used when
specifying ALL volumes
Cause:
The FORCE option was used to disable ALL volumes.
Action:
Use FORCE option to disable one volume at a time.
ORA-15456: missing or invalid volume usage
specifier
Cause:
The command did not specify a valid volume usage string.
Action:
Specify a valid volume usage string with alphanumeric characters.
ORA-15457: first letter of the volume name is not
alphabetic
Cause:
A volume name was specified with a nonalphabetic first character.
Action:
Set the first character of the volume name to be alphabetic.
ORA-15458: invalid character in volume name
Cause:
A volume name was specified with an invalid character.
Action:
Use a volume name with only alphanumeric characters.
ORA-15459: STRIPE_WIDTH of string is not a
power of two
Cause:
An ADD VOLUME command specified a STRIPE_WIDTH that was not a power of two.
Action:
Select a STRIPE_WIDTH that is a power of two; for example, 4K, 8K, etc.
ORA-15460: volume name 'string' is already
in use
Cause:
An ADD VOLUME command specified a volume name that was already used by another
volume.
Action:
Select a different name for the volume.
ORA-15461: STRIPE_WIDTH of string bytes is
less than the minimum of string bytes
Cause:
An ADD VOLUME command specified a STRIPE_WIDTH that was too small.
Action:
Select a larger STRIPE_WIDTH.
ORA-15462: STRIPE_WIDTH of string bytes is
greater than the maximum of string bytes
Cause:
An ADD VOLUME command specified a STRIPE_WIDTH that was too large.
Action:
Select a smaller STRIPE_WIDTH.
ORA-15463: volume size of stringK is less
then the minimum of stringM
Cause:
The volume size specified was too small.
Action:
Select a larger volume size.
ORA-15464: STRIPE_COLUMNS of string is
greater than the maximum of string
Cause:
An ADD VOLUME command specified a STRIPE_COLUMNS that was that was too large.
Action:
Select a smaller STRIPE_COLUMNS value.
ORA-15465: STRIPE_COLUMNS of string is less
than the minimum of string
Cause:
An ADD VOLUME command specified a STRIPE_COLUMNS that was too small.
Action:
Select a larger STRIPE_COLUMNS value.
ORA-15466: volume name 'string' does not
exist
Cause:
The command specified a volume name that does not exist.
Action:
Ensure a valid volume name is used.
ORA-15467: volume operation is already in progress
Cause:
Another command is currently operating on the specified volume.
Action:
Wait a short time before retrying the command.
ORA-15468: operation not permitted; volume 'string'
currently being accessed
Cause:
An attempt was made to communicate with the volume driver. The volume was being
accessed by another application and, therefore, could not be changed.
Action:
Shut down all applications that might be accessing this volume and then retry
the command.
ORA-15469: VBG process terminated with error
Cause:
A volume background process terminated with error.
Action:
Wait for process to restart.
ORA-15470: VDBG process terminated with error
Cause:
The volume driver background process terminated with error.
Action:
Warm start instance.
ORA-15471: volume redundancy incompatible with
diskgroup redundancy
Cause:
An ADD VOLUME command specified a volume redundancy that was incompatible with
the diskgroups redundancy.
Action:
Specify a valid volume redundancy. A volume cannot have external redundancy
with a high redundancy diskgroup. Also, a volume cannot have high redundancy
with an external redundancy diskgroup.
ORA-15472: volume library cannot be loaded.
Platform may not support volume creation.
Cause:
The volume library could not be loaded. Either the platform does not support
volume operations, or there is a problem with the library.
Action:
Ensure that the platform supports volumes. If the platform does support
volumes, check the alert log for library loading failure information.
ORA-15473: access to a volume's storage through an
unsupported interface
Cause:
An attempt was made to access or modify a volume's storage through an
unsupported interface.
Action:
Use supported interfaces for access to volume devices.
ORA-15474: volume name is greater than string
characters
Cause:
An ADD VOLUME command specified a volume name that was too long.
Action:
Select a smaller volume name.
ORA-15475: usage string is greater than string
characters
Cause:
The usage string specified was too long.
Action:
Select a smaller usage string.
ORA-15476: resize of OFS volume must use OFS resize
command
Cause:
An attempt was made to resize an OFS volume through SQL.
Action:
Use the supported OFS commands to resize the volume.
ORA-15477: cannot communicate with the volume
driver
Cause:
An attempt was made to communicate with the volume driver.
Action:
Check that the ASM volume driver is loaded. If so, check the alert log to
identify the reason for failure and take necessary action to prevent such
failures in the future.
ORA-15478: OFSC process terminated with error
Cause:
The ofs background process terminated with error
Action:
Wait for process restart
ORA-15479: diskgroup version incompatible with ASM
volumes
Cause:
The diskgroup's version was incompatible with creating volumes.
Action:
Upgrade the diskgroup version in order to use volume functionality.
ORA-15480: error reported in the ASM volume driver
Cause:
An error was reported in the ASM volume driver.
Action:
Check the operating system log files to identify the reason for the failure and
take necessary action to prevent such failures in the future.
ORA-15481: missing or invalid volume mountpath
specifier
Cause:
A invalid volume mountpath string was specified.
Action:
Specify a valid volume mountpath string with alphanumeric characters.
ORA-15482: failed to create/remove path to volume
device file
Cause:
Improper driver installation.
Action:
Check the alert log for device file creation failure information. Reload the
driver using the supported installation method.
ORA-15501: cannot start workload capture on
instance string
Cause:
Given instance encountered unexpected errors while trying to start the workload
capture.
Action:
Check the alert log and other diagnostics in the given instance to diagnose the
problem.
ORA-15502: cannot stop workload capture on instance
string
Cause:
Given instance encountered unexpected errors while trying to stop the workload
capture.
Action:
Check the alert log and other diagnostics in the given instance to diagnose the
problem.
ORA-15503: cannot startup instance when procedures
in "DBMS_WORKLOAD_CAPTURE" or "DBMS_WORKLOAD_REPLAY" are in
the middle of their execution
Cause:
The new instance could not be started because the database was executing a
procedure in either the DBMS_WORKLOAD_CAPTURE or DBMS_WORKLOAD_REPLAY package.
Action:
Start the new instance after such procedures in the given packages have
finished execution.
ORA-15504: cannot start workload capture because
instance string not present in RESTRICTED SESSION mode
Cause:
The NO_RESTART_MODE option in DBMS_WORKLOAD_CAPTURE.START_CAPTURE was FALSE,
therefore all the active instances were expected to be in the RESTRICTED
SESSION mode.
Action:
Start all instances using STARTUP RESTRICT or execute ALTER SYSTEM ENABLE
RESTRICTED SESSION on all active instances before issuing
DBMS_WORKLOAD_CAPTURE.START_CAPTURE.
ORA-15505: cannot start workload capture because
instance string encountered errors while accessing directory "string"
Cause:
Given instance could not access the specified CAPTURE directory or the
specified CAPTURE directory already had a workload capture in it.
Action:
Provide a directory object that is valid, empty and accessible from all the
instances in the database cluster.
ORA-15506: cannot prepare instance string
for replay
Cause:
Given instance encountered unexpected errors while trying to prepare for a
workload replay.
Action:
Check the alert log and other diagnostics in the given instance to diagnose the
problem.
ORA-15507: cannot start workload replay on instance
string
Cause:
Given instance encountered unexpected errors while trying to start a workload
replay.
Action:
Check the alert log and other diagnostics in the given instance to diagnose the
problem.
ORA-15508: cannot cancel workload replay on
instance string
Cause:
Given instance encountered unexpected errors while trying to cancel a workload
replay.
Action:
Check the alert log and other diagnostics in the given instance to diagnose the
problem.
ORA-15509: workload replay has been cancelled
Cause:
Workload replay was cancelled.
Action:
Restart the workload replay.
ORA-15510: cannot perform operation when
"STATISTICS_LEVEL" is "BASIC"
Cause:
The STATISTICS_LEVEL initialization parameter was set to BASIC.
Action:
Change the STATISTICS_LEVEL initialization parameter setting to either TYPICAL
or ALL.
ORA-15511: cannot process workload capture because
no user sessions were recorded
Cause:
No user sessions were recorded in the given workload capture. Processing this
capture failed because no user workload was captured.
Action:
Capture a workload in which at least one user session connects and performs
some operations.
ORA-15512: directory "string" does
not contain a valid processed workload capture
Cause:
One or more files created by DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE were missing.
Action:
Process the workload capture using DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE and
then retry the command.
ORA-15513: cannot access the input directory
Cause:
Given input directory is either invalid or inaccessible.
Action:
Verify that the input directory is valid and accessible and then retry the
command.
ORA-15514: cannot find a match for the remote
procedure call during replay
Cause:
The corresponding PL/SQL program was either dropped or modified.
Action:
Verify that the corresponding PL/SQL program is defined the same way during
replay as it was defined during workload capture.
ORA-15515: error while replaying remote procedure
call: "string.string.string"
Cause:
Error encountered during the replay of a remote procedure call.
Action:
Correct the cause of the preceding error and restart workload replay.
ORA-15516: parallel preprocessing worker hit error
ORA-string
Cause:
One of the parallel preprocessing workers died unexpectedly while processing
the workload.
Action:
Find the root cause or simply preprocess the workload using only one process.
ORA-15517: cannot start parallel preprocessing
worker
Cause:
One of the parallel preprocessing workers could not be started.
Action:
Find the root cause or simply preprocess the workload using only one process.
ORA-15518: parallel preprocessing encountered an
unexpected error
Cause:
An unexpected error occured during parallel preprocessing.
Action:
Find the root cause or simply preprocess the workload using only one process.
ORA-15551: workload replay client cannot connect to
database server
Cause:
The server connection identifier was invalid.
Action:
Restart the client with correct server connection identifier.
ORA-15552: workload replay client cannot login to
database server
Cause:
1) the replay client used an invalid username or password; 2) the replay user
does not have the privilege to switch user; 3) the recorded username does not
exist in the replay database.
Action:
1) restart replay client with correct username and password 2) grant user
switching prvilege to the replay user 3) verify whether the replay database was
restored properly
ORA-15553: workload replay client cannot execute
the DBMS_WORKLOAD_REPLAY package
Cause:
Workload Replay Client's replay user did not have EXECUTE permission on the
DBMS_WORKLOAD_REPLAY package.
Action:
Grant execute permission on the DBMS_WORKLOAD_REPLAY package to replay user and
restart the Workload Replay Client.
ORA-15554: cannot start workload replay client
because the database server is not in PREPARE mode
Cause:
The Workload Replay Client could not connect to the database server because the
database server was not in the PREPARE mode.
Action:
Put the database in PREPARE mode by using DBMS_WORKLOAD_REPLAY.PREPARE_REPLAY,
and restart the Workload Replay Client.
ORA-15555: workload replay client encountered
unexpected error: "string"
Cause:
Workload Replay Client encountered an unexpected error.
Action:
Check the Workload Replay Client's log files and the database server alert log
to diagnose the problem.
ORA-15556: invalid input specified to the workload
replay client
Cause:
Invalid input was specified.
Action:
Use the Workload Replay Client's HELP=Y option to know more about valid input
options.
ORA-15557: workload replay client cannot access the
replay directory or the database version do not match the preprocessing one
Cause:
The Workload Replay Client could not access the directory that contained the
workload to be replayed, or the workload was preprocessed by a different
version of the database.
Action:
Restart the workload replay after specifying the correct replay directory, or
preprocess it with the correct database.
ORA-15558: replay thread encountered unexpected
error
Cause:
A single replay thread got disconnected from the server due to an unexpected
error.
Action:
Check the Workload Replay Client's log files and the database server alert log
to diagnose the problem.
ORA-15559: workload replay client cannot open
workload capture file
Cause:
The Workload Replay Client could not access one or more workload capture files
from the replay directory.
Action:
Restart the workload replay after copying all the workload capture files to the
replay directory.
ORA-15560: workload replay client cannot access the
work directory
Cause:
The Workload Replay Client could not access the work directory to write log
files for debug information.
Action:
Restart the Workload Replay Client after specifying the correct work directory.
ORA-15561: workload replay client cannot connect to
the remapped connection with conn_id : string
Cause:
The specified connection is invalid or the specified host is inaccessible.
Action:
Test the specified connection using other methods and redefine the connection
remapping, if necessary. Consult the view DBA_WORKLOAD_CONNECTION_MAP to
inspect connection remappings.
ORA-15562: workload replay client cannot read the
DBA_WORKLOAD_CONNECTION_MAP view
Cause:
The DBA_WORKLOAD_CONNECTION_MAP view did not exist or was not accessible.
Action:
Re-create the workload capture and replay views. For additional information,
see the documentation.
ORA-15563: workload replay client cannot spawn new
threads
Cause:
The Workload Replay Client does not have enough resource (CPU or memory) to
spawn new threads.
Action:
Restart the workload replay after allocating more resource (CPU and memory) to
the Workload Replay Client or use more hosts as replay clients to drive the
workload.
ORA-15564: contents of the replay directory
provided to the workload replay client do not match with the replay directory
provided to the database server
Cause:
The processed workload capture files given to the workload replay client
directory did not match the contents of the replay directory given as input to
DBMS_WORKLOAD_REPLAY.INITIALIZE_REPLAY.
Action:
Provide the same processed workload capture files to both the database server
and all the workload replay clients and restart the replay. If the same
workload capture files were processed more than once, provide a copy of the
latest processed workload capture files to all the workload replay clients and
the database server.
ORA-15566: workload replay client cannot replay
user call in the current version
Cause:
The workload replay client encountered a user call in the captured workload
that was not supported for replay in the current version.
Action:
Look in the DBA_WORKLOAD_REPLAY_DIVERGENCE view for details about the call that
encountered this error. Refer to the documentation for more details on the
types of workload that are not supported in the current version.
ORA-15590: encountered an incomplete workload
capture file
Cause:
The captured workload contained one or more incomplete recording files. This
can happen when the original workload capture's FINISH_CAPTURE command timed
out while waiting for all the active sessions to close their workload capture
files.
Action:
Incomplete capture files will not interfere with the processing and replaying
of the captured workload. This is simply a warning message to point out that
some database calls might not have been recorded due to FINISH_CAPTURE command
timing out.
ORA-15601: Invalid value specified for parameter
"string"
Cause:
An invalid value was specified for the given parameter.
Action:
Correct the value being specified for the parameter.
ORA-15602: Parameter "string"
cannot be NULL.
Cause:
An attempt was made to call a procedure without a required parameter.
Action:
Specify a valid value for this parameter.
ORA-15603: Action cannot be performed when database
is in read-only mode.
Cause:
A procedure in DBMS_AUTO_TASK_ADMIN package was invoked when database was open
in read-only mode.
Action:
Retry when database is open in read/write mode.
ORA-15604: Initialization parameters prevent client
from being enabled.
Cause:
An attempt was made to enable a client that was disabled for automatic
execution by an initialization parameter.
Action:
Check the related client parameters and try again.
ORA-15605: "string" is not a Maintenance
Window
Cause:
Window name passed to DBMS_AUTO_TASK_ADMIN.ENABLE procedure must be a member of
the MAINTENANCE_WINDOW_GROUP.
Action:
Make the window a member of the MAINTENANCE_WINDOW_GROUP and retry the call.
ORA-16000: database open for read-only access
Cause:
The database has been opened for read-only access. Attempts to modify the
database using inappropriate DML or DDL statements generate this error.
Action:
In order to modify the database, it must first be shut down and re-opened for
read-write access.
ORA-16001: database already open for read-only
access by another instance
Cause:
The database has been opened for read-only access by another instance, and
cannot be opened for read-write access by this instance.
Action:
This instance must be opened for read-write access, or all other instances must
first be shut down and re-opened for read-only access.
ORA-16002: database already open for read-write
access by another instance
Cause:
The database has been opened for read-write access by another instance, and
cannot be opened for read-only access by this instance.
Action:
This instance must be opened for read-only access, or all other instances must
first be shut down and re-opened for read-write access.
ORA-16003: standby database is restricted to
read-only access
Cause:
To ensure its integrity, a standby database can only be opened for read-only
access.
Action:
Re-issue the ALTER DATABASE OPEN specifying READ ONLY.
ORA-16004: backup database requires recovery
Cause:
The control file is for a backup database which requires recovery, and cannot
be opened for read-only access by this instance.
Action:
Perform the necessary recovery and re-open for read-only access.
ORA-16005: database requires recovery
Cause:
The database requires recovery, and therefore cannot be opened for read-only
access by this instance.
Action:
Perform the necessary recovery and re-open for read-only access.
ORA-16006: audit_trail destination incompatible
with database open mode
Cause:
The audit_trail initialization parameter was set to "DB" (or TRUE),
which is incompatible with a database opened for read-only access.
Action:
When the database is opened for read-only access, the audit_trail
initialization parameter can only be set to "OS" or "NONE"
(FALSE).
ORA-16007: invalid backup control file checkpoint
Cause:
The backup control file being opened for read-only access does not contain a
valid control file checkpoint. Therefore the database cannot be opened for
read-only access.
Action:
First open the database for read-write access which will result in valid
control file checkpoint. Then re-open the database for read-only access.
ORA-16008: indeterminate control file checkpoint
Cause:
The control file for the database being opened for read-only access was created
via CREATE CONTROLFILE. Therefore a control file checkpoint could not be
calculated and the database cannot be opened for read-only access.
Action:
First open the database for read-write access which will result in valid
control file checkpoint. Then re-open the database for read-only access.
ORA-16009: remote archive log destination must be a
STANDBY database
Cause:
The database associated with the archive log destination service name is other
than the required STANDBY type database. Remote archival of redo log files is
not allowed to non-STANDBY database instances.
Action:
Take the necessary steps to create the required compatible STANDBY database
before retrying the ARCHIVE LOG processing.
ORA-16011: Archivelog Remote File Server process in
Error state
Cause:
The archivelog remote file server (RFS) process at the specified standby
database site has experienced an unrecoverable error and is unable to receive
further archive log data.
Action:
Correct the problem at the standby database site.
ORA-16012: Archive log standby database identifier
mismatch
Cause:
The database identifiers of the Primary and Standby database do not match.
Remote archival of redo log files is not allowed to incompatible STANDBY
database instances.
Action:
Take the necessary steps to create the required compatible STANDBY database
before retrying the ARCHIVE LOG processing.
ORA-16013: log string sequence# string
does not need archiving
Cause:
An attempt was made to archive the named file manually, but the file did not
require archiving. The file had previously been successfully archived.
Action:
No action is required.
ORA-16014: log string sequence# string
not archived, no available destinations
Cause:
An attempt was made to archive the named log, but the archive was unsuccessful.
The archive failed because there were no archive log destinations specified or
all destinations experienced debilitating errors.
Action:
Verify that archive log destinations are being specified and/or take the
necessary step to correct any errors that may have occurred.
ORA-16015: log string sequence# string
not archived, media recovery disabled
Cause:
An attempt was made to archive the named log, but the archive was unsuccessful.
A standby archive log destination was specified and the database was not media
recovery enabled. This is not allowed.
Action:
Disable the standby destination or enable media recovery and retry.
ORA-16016: archived log for thread string
sequence# string unavailable
Cause:
The managed standby database recovery operation has timed out waiting for the
requested archived log file.
Action:
Verify that the primary database is still archiving redo logs to the standby
recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command.
ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST
without a primary archive destination
Cause:
The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the
primary archive destination was set to NULL explicitly.
Action:
Set the primary archive destination to a valid non-NULL value.
ORA-16018: cannot use string with
LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
Cause:
One of the following events caused an incompatibility: 1) Parameter
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a
LOG_ARCHIVE_DEST_n (n = 1...10) parameter was encountered while fetching
initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was
in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching
initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an
ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST
or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in
use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to
define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.
Action:
Eliminate any incompatible parameter definitions.
ORA-16019: cannot use string with
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
Cause:
One of the following events caused an incompatibility: 1) Parameter
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified
LOG_ARCHIVE_DEST_n (n = 1...10) or DB_RECOVERY_FILE_DEST parameter was
encountered while fetching initialization parameters. 2) Parameter
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made
to use an ALTER SYSTEM or ALTER SESSION command to define a value for the
specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER
SYSTEM ARCHIVE LOG START TO command was in effect when the specified
LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization
parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when
an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a
value for the specified LOG_ARCHIVE_DEST_n parameter.
Action:
Eliminate any incompatible parameter definitions.
ORA-16020: less destinations available than
specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
Cause:
With automatic archiving enabled, the number of archive log destinations that
could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST
parameter value.
Action:
Either adjust the settings of the log archive destination parameters, or lower
the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.
ORA-16021: session string destination cannot
be the same as session string destination
Cause:
An attempt was made to change the first specified archive log parameter using
ALTER SESSION to have a destination value that duplicates the session-level
destination value of the second specified archive log parameter.
Action:
Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n
parameters.
ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because
LOG_ARCHIVE_DUPLEX_DEST is non-NULL
Cause:
An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter
LOG_ARCHIVE_DUPLEX_DEST is non-NULL.
Action:
Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter
LOG_ARCHIVE_DUPLEX_DEST to a NULL value.
ORA-16023: system string destination cannot
be the same as session string destination
Cause:
An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...10)
parameter produced a destination that duplicates the session destination value
of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when
setting a non-NULL value with the ALTER SYSTEM command. Or, this error can
occur when setting a NULL value with ALTER SESSION command, because then the
associated system destination value may appear as a duplicate.
Action:
Specify a different destination value for the first specified
LOG_ARCHIVE_DEST_n parameter.
ORA-16024: parameter string cannot be parsed
Cause:
The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter could not
be parsed. Common causes for this error are a misplaced equal sign, an
unrecognized attribute, or an attribute that is missing a required value.
Action:
Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16025: parameter string contains
repeated or conflicting attributes
Cause:
The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained
either repeated attributes or attributes that conflicted with each other.
Action:
Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16026: parameter string contains an
invalid attribute value
Cause:
The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained
an attribute with an invalid value.
Action:
Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16027: parameter string is missing a
destination option
Cause:
The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter failed to
include a destination option. A destination option is specified using either
the LOCATION or SERVICE attrbute.
Action:
Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16028: new string causes less
destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
Cause:
With automatic archiving enabled, an attempt was made to change the indicated
LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...10) to a
value that reduces the number of archive log destinations to less than the
specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.
Action:
Either select different options for the LOG_ARCHIVE_DEST_n or
LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter
LOG_ARCHIVE_MIN_SUCCEED_DEST.
ORA-16029: cannot change
LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
Cause:
An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when
there are no archive log destinations.
Action:
Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST,
LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1...10). Then, change the
value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.
ORA-16030: session specific change requires a
LOG_ARCHIVE_DEST_n destination
Cause:
The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or
LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the
LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.
Action:
Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with
LOG_ARCHIVE_DEST_n (n = 1...10) parameters.
ORA-16031: parameter string destination string
exceeds string character limit
Cause:
The value for the specified parameter contained a destination string that is
too long.
Action:
Replace the destination value for the specified parameter with a character
string that has a length below the limit specified in the error message.
ORA-16032: parameter string destination
string cannot be translated
Cause:
The value for the specified parameter contained a destination string that could
not be translated.
Action:
Use a valid destination string in the specified parameter.
ORA-16033: parameter string destination
cannot be the same as parameter string destination
Cause:
An attempt was made to change the first specified archive log parameter to have
a destination value that duplicates the system-level destination value of the
second specified archive log parameter.
Action:
Specify a different value for one of the archive log parameters.
ORA-16034: FROM parameter is incompatible with
MANAGED recovery
Cause:
Use of the FROM 'location' parameter is not allowed when MANAGED recovery has
been specified.
Action:
Correct the syntax and retry the command.
ORA-16035: missing required keyword string
Cause:
The indicated keyword is required but was not specified.
Action:
Correct the syntax and retry the command.
ORA-16036: invalid MANAGED recovery CANCEL option
Cause:
A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED
STANDBY DATABASE statement.
Action:
Specify either nothing or IMMEDIATE following CANCEL.
No hay comentarios:
Publicar un comentario