Sep 19 2016

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-15400 to ORA-15600

Category: Errors and SolutionsFatih Acar @ 21:12

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-15400 to ORA-15600

ORA-15400: not running on supported ASM appliance

Cause: An attempt was made to initialize the server code as an appliance when it was not running a supported appliance configuration.

Action: Check the appliance configuration and retry the operation.

ORA-15401: command not supported on ASM appliance ‘string

Cause: An attempt was made to run an operation that is not supported by the specified appliance.

Action: Check the documentation to see which operations are allowed or disallowed for the specified appliance.

ORA-15402: insufficient number of disks to support ASM appliance ‘string

Cause: An attempt was made to do an operation that resulted in insufficient number of disks required for the specified appliance.

Action: Check the appliance configuration and retry the operation after inserting disks in the appropriate slots.

ORA-15403: unable to read an ASM appliance configuration file

Cause: Oracle ASM was unable to read an appliance configuration file.

Action: Check the operating system error messages to determine the identity of the configuration file. Then, fix the configuration file.

ORA-15404: Oracle ASM could not add disk “string” to disk group “string” on appliance string

Cause: There were too many dropping or offline disks in the specified disk group.

Action: Wait for the drop and rebalance operations to complete, or online the offline disks and wait for the online to complete. Then, retry the operation.

ORA-15405: Slot string in Oracle ASM appliance ‘string‘ contains more than one disk

Cause: An attempt was made to add a disk to a slot in the ASM appliance that already had a disk (possibly OFFLINE) associated with it.

Action: Use FORCE to drop the disk that exists in the specified slot. Then, retry the operation.

ORA-15406: ASM disk string is being replaced.

Cause: An attempt was made to either online or replace a disk that was already being replaced, probably by another instance.

Action: Change the ONLINE statement to exclude the disk.

ORA-15407: Disk specification ‘string‘ matches multiple disks.

Cause: More than one disk is discovered matching the specified disk string.

Action: Change the disk string to specify one and only one disk.

ORA-15408: Replacement disk ‘string‘ for ‘string‘ must be at least string MB.

Cause: The replacement disk must be at least of the same size of the old disk.

Action: Use a larger physical disk to replace.

ORA-15409: All disks in disk group string are not of the same type.

Cause: An attempt was made to add disks of a different type to the disk group under appliance mode.

Action: Check if all the disks in the disk group are of the same type. Do not add flash and hard disks to the same disk group.

ORA-15410: Disks in disk group string do not have equal size.

Cause: The disks in the disk group were not of equal size.

Action: Ensure that all disks in the disk group are of equal size. If adding new disks to the disk group, their size must be equal to the size of the existing disks in the disk group. If resizing, all disks in the disk group must be resized to the same size.

ORA-15411: Failure groups in disk group string have different number of disks.

Cause: An attempt was made to enable appliance mode with a different number of disks in each failure group.

Action: Check if all failure groups have an equal number of disks and try again.

ORA-15412: Operation on disk group string is incompatible under appliance mode.

Cause: An attempt was made to do an operation that resulted in dropping all disks in a failure group or creating a new failure group.

Action: Disable appliance mode, perform the operation and reenable appliance mode. WARNING: To reenable appliance mode, ensure the following constraints are met: * There are a sufficient number of disks in each failure group. * All failure groups have an equal number of disks. * There are no offline disks in the disk group. * Every disk in the disk group is of the same type (flash or hard disk). * All disks in the disk group have an equal size.

ORA-15413: Appliance mode is disabled.

Cause: Appliance mode could not be set because it was explicitly disabled.

Action: Enable appliance mode and appliance partnering parameters.

ORA-15414: Appliance mode requires at least string failure groups and either string or string disks in all failure groups.

Cause: Appliance mode could not be enabled because it did not meet the minimum requirements.

Action: Check if there are sufficient failure groups and a sufficient number of disks in each failure group.

ORA-15415: could not retrieve appliance properties for disk group string

Cause: Some of the appliance properties were invalid. This could be due to a cell software downgrade after setting the ‘appliance.mode’ attribute.

Action: Check the cell software on all of the cells or disable appliance mode.

ORA-15416: ASM disk string in disk group string is offline.

Cause: An offline disk prevented the current ADD or DROP operation.

Action: Drop the offline disk or online the offline disk or disable appliance mode.

ORA-15418: Appliance mode is not supported for compatible.asm string.

Cause: Appliance mode could not be enabled for the current value of the compatible.asm attribute.

Action: Disable appliance mode if it is enabled or advance compatible.asm to a version that supports appliance mode.

ORA-15419: disk group string is not mounted in restricted mode

Cause: The specified disk group was not mounted in restricted mode prohibiting the requested operation.

Action: Dismount the disk group, remount it in restricted mode and retry the operation.

ORA-15420: Operation on disk group string is disabled.

Cause: The current operation could not be completed because the disk group is in the middle of an appliance migration.

Action: Wait for the migration to complete and then retry the command.

ORA-15421: string is not supported when the disk group is mounted for recovery.

Cause: The disk group was mounted for recovery preventing the requested operation.

Action: Dismount the disk group, remount it in normal mode and retry the operation.

ORA-15422: Disks ‘string‘ and ‘string‘, in failure group ‘string‘ of disk group ‘string‘, do not belong to the same cell

Cause: It was detected that disks from different cells belong to the same failure group.

Action: Make the necessary disk swaps so only disks from the same cell belong to the same failure group.

ORA-15423: Disk ‘string‘ in failure group ‘string‘ and disk ‘string‘ in failure group ‘string‘ of disk group ‘string‘ belong to the same cell

Cause: It was detected that disks from the same cell belong to different failure groups.

Action: Make the necessary disk swaps so disks from the same cell are not shared between different failure groups.

ORA-15430: missing or invalid quota group name

Cause: The command did not specify a valid quota group name.

Action: Specify a valid quota group name.

ORA-15431: missing or invalid quota group property

Cause: The command did not specify a valid quota group property.

Action: Specify a valid quota group property.

ORA-15432: missing or invalid quota

Cause: The command did not specify a valid quota limit for the quota group.

Action: Specify a valid quota limit.

ORA-15433: missing or invalid file group name

Cause: The command did not specify a valid file group name.

Action: Specify a valid file group name.

ORA-15434: quota group string already exists in disk group string

Cause: The specified quota group already existed in the disk group.

Action: Specify a different quota group name.

ORA-15435: quota group string does not exist in disk group string

Cause: The specified quota group did not exist in the disk group.

Action: Specify a valid quota group name.

ORA-15436: invalid operation on quota group string

Cause: The specified operation was not permitted on the quota group.

Action: Check the quota group specified in the command.

ORA-15437: Not enough quota available in quota group string.

Cause: The specified quota group did not have sufficient quota available to permit the operation.

Action: Specify a quota group with sufficient available quota or increase the quota limit of the specified quota group.

ORA-15438: Quota group string has one or more file groups associated.

Cause: One or more file groups were associated with the specified quota group and, therefore, the operation was not permitted.

Action: Drop the file groups or move the file groups to a different quota group.

ORA-15440: VIO0 process terminated with error

Cause: A volume IO background process terminated with error.

Action: Wait for the process to restart.

ORA-15442: The ASM rebalance phase string does not exist.

Cause: The specified ASM rebalance phase did not exist.

Action: Specify a valid rebalance phase.

ORA-15443: The ASM rebalance phase string cannot be skipped.

Cause: The specified ASM rebalance phase cannot be skipped.

Action: Specify a valid rebalance phase to skip.

ORA-15444: Volume string needs to be online and mounted to complete the operation.

Cause: The operation could not be completed with the volume offline or dismounted.

Action: Online or mount the volume and retry the operation.

ORA-15445: Volume string does not allow sector size migration.

Cause: Sector size migration was not allowed because Oracle ACFS accelerator volumes, volumes associated with an Oracle ACFS accelerator, or non Oracle ACFS volumes exist in the disk group.

Action: Move the volume to a different disk group and retry the operation. 15446 available 15447 available 15448 available 15449 available

ORA-15450: invalid volume name specifier

Cause: The volume name specified was invalid

Action: Specify a valid volume name.

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 than 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 ‘string‘ in disk group ‘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 was currently operating on a volume.

Action: Wait a short time before retrying the command.

ORA-15468: volume ‘string‘ in diskgroup ‘string‘ is 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 disk group redundancy

Cause: An ADD VOLUME command specified a volume redundancy that was incompatible with the redundancy of the disk group.

Action: Specify a valid volume redundancy. An unprotected redundancy volume cannot be added to a normal or high redundancy disk group, and a mirror or high redundancy volume cannot be added to an external redundancy disk group.

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: ACFS volumes must be resized with the ‘acfsutil size’ operating system command.

Cause: An attempt was made using SQL to resize an ADVM volume that contains an ACFS file system.

Action: Use the ‘acfsutil size’ operating system command 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: ACFS process terminated with error

Cause: The ACFS background process terminated with error

Action: Wait for process restart

ORA-15479: ASM diskgroup does not support volumes

Cause: Volumes were not supported. A common example is having disks, such as NFS, in the diskgroup that are not supported by volumes.

Action: Remove unsupported disks in the diskgroup.

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 device file for volume string on diskgroup string

Cause: Improper driver installation.

Action: Check the alert log for device file creation failure information. Reload the driver using the supported installation method.

ORA-15483: volume driver version is not compatible with the ASM instance

Cause: The version of the ASM volume driver was not supported by ASM.

Action: Update the volume driver or the ASM instance.

ORA-15484: volume ‘string‘ contains string error(s)

Cause: Errors were returned by the ALTER DISKGROUP CHECK VOLUME command.

Action: See the alert log for details of the errors.

ORA-15485: number of volumes in diskgroup exceeds the maximum of string

Cause: A volume was added on a diskgroup that already contained the maximum number allowed.

Action: Remove volumes on the diskgroup.

ORA-15486: internal error while altering volume

Cause: An internal ASM error occurred while altering a volume.

Action: See the alert log for details of the error.

ORA-15487: cannot shutdown the ASM instance with an open ASM volume

Cause: One or more ASM volumes were found to be open during shutdown.

Action: Close the ASM volume and retry the shutdown.

ORA-15488: volume string is open on instance string

Cause: ASM volume was not closed prior to instance termination on node specified.

Action: Close the ASM volume either via unmount or node restart and retry the operation

ORA-15489: conflicting volume already open on this node

Cause: An ASM volume was not closed prior to instance shutdown on node specified. It is conflicting with the volume that is to be enabled.

Action: Close the ASM volume either via unmount or node restart and retry the operation.

ORA-15490: not all instances could add/drop the volume

Cause: The ASM volume cannot be added/dropped on all instances.

Action: See the alert log for the reason the volume could not be added/droped.

ORA-15491: volume redundancy conflicts with disk region options

Cause: Non-mirrored volumes erroneously contained the MIRRORHOT or MIRRORCOLD keyword.

Action: Remove the MIRRORHOT or MIRRORCOLD keywords from non-mirrored volumes.

ORA-15492: command or option incompatible with ASM volumes

Cause: An attempt was made to use a feature which is not compatible with existing ASM volumes. A common example is adding a disk to the diskgroup that is unsupported by ASM volumes.

Action: Omit the option from the command.

ORA-15493: target ADVM compatibility (string) exceeds ASM compatibility (string)

Cause: An attempt was made to advance ADVM compatibility beyond the disk group’s ASM compatibility.

Action: Advance ASM compatibility before advancing ADVM compatibility.

ORA-15494: compatible.advm must be string or higher

Cause: An attempt was made to set the ADVM compatibility to a version that was lower than the minimum supported.

Action: Set ADVM compatibility to at least the minimum supported version.

ORA-15495: ASM operation requires compatible.advm of string or higher

Cause: The ASM operation specified required a higher disk group attribute value for compatible.advm.

Action: Set the disk group attribute compatible.advm to or above the requested version.

ORA-15496: volume size is greater than the maximum of stringT

Cause: The volume size specified was too large.

Action: Select a smaller volume size.

ORA-15497: Volume string uses a metadata block size (string) smaller than the specified sector size (string).

Cause: The Oracle ACFS volume had a metadata block size incompatible with the specified sector size.

Action: Migrate Oracle ACFS to a larger metadata block size before changing the sector size.

ORA-15498: Volume name ‘string‘ would collide with existing volume(s) ‘string string‘.

Cause: A volume name was specified that would conflict with existing volume device(s). A volume ‘<vol_name>-<dg_num>’ is the name of the block device. Additionally, a raw device named ‘r<vol_name>-<dg_num>’ is also created. Since that name already existed, a name collision occurred.

Action: Choose another name for the volume (no leading ‘r’ is recommended).

ORA-15499: Volume Membership (VMB) process terminated with error

Cause: The volume driver background process terminated with error.

Action: Warm start the instance.

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 occurred during parallel preprocessing.

Action: Find the root cause or simply preprocess the workload using only one process.

ORA-15519: cannot access database link “string” because it is disabled

Cause: For security considerations, access to external databases via database links were disabled during workload replay.

Action: Use advanced parameter for Database Replay to enable database links during workload replay.

ORA-15520: Directory is corrupted. Two WMD files are found at “string” and “string

Cause: Two WMD files were found in the directory.

Action: Check that the WMD files in capture directory were not modified, moved, duplicated or deleted.

ORA-15521: failed to create file “string” during workload processing

Cause: An attempt was made to create a file during workload processing without the proper file permissions.

Action: Correct the file permissions and try again.

ORA-15522: failed to generate a workload capture subset: “string

Cause: An attempt to generate a workload capture subset failed. Possible reasons are included in the error message.

Action: Correct the issue and try again.

ORA-15523: failed to create subpath “string” under path “string

Cause: Either the path does not exist or is inaccessible or the subpath specification is invalid.

Action: Verify that the path exists and is accessible, the subpath specification is valid, and retry the command.

ORA-15525: a user call cannot be replayed because not enough information was captured; extra details: string

Cause: An attempt to replay a user call failed because the workload was captured with an old version of Oracle. The information needed for replay was not recorded.

Action: Capture the workload using a newer version of Oracle or use the replay filters to skip the user call.

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; type ‘wrc HELP=Y’ for help

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-15567: replay user string encountered an error during a sanity check

Cause: The replay user encountered an error when accessing internal objects for Database Replay or switching user.

Action: Set up the replay user appropriately at the replay database. Ensure that the replay user can access SYS-owned objects and has been granted the BECOME USER privilege.

ORA-15568: login of user string during workload replay failed with ORA-string

Cause: The recorded user did not exist in the replay database or encountered other problems during log in.

Action: Check the returned error number and set up the recorded user appropriately at the replay database.

ORA-15569: timeout encountered during the replay of a recorded user call

Cause: The replay of a recorded user call was terminated since it was significantly slower than the workload capture.

Action: Find the root cause for the performance issue. Or, use DBMS_WORKLOAD_REPLAY API to disable the timeout check if the replay is expected to be slower.

ORA-15590: encountered incomplete workload capture files

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. For a list of the incomplete files, check the alert log for lines containing DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing.

ORA-15591: encountered corrupt workload capture files

Cause: The captured workload contained one or more corrupt recording files.

Action: For a list of the incomplete files, check the alert log for lines containing DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing. The corrupt files will be replayed up to the point of the corruption. Alternatively, it is possible to remove the corrupt files and run DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE again. In this case, no workload from the corrupt files will be replayed.

12,195 total views, 10 views today

Tags: Oracle Error Solutions

facebook comments:

Leave a Reply

Time limit is exhausted. Please reload CAPTCHA.