This book lists Event Log messages in numeric order. The message number is the number that appears at the beginning of the second line of the message you see in the Event Log. In this book, the message number is followed by the message text, which is the last line you see in the Event Log message. For a description of the complete message that you see in the Event Log, go to "Format for Messages".
Each message description in this book contains the following information:
The message number and message text
An explanation of the message
A description of any variables appearing in the message
Any action necessary to respond to the message
All Event Log entries have a consistent format. Each entry contains a one-line prefix followed by module information and two or more lines of message text.
The first line of the message contains three elements:
The mm-dd-yy hh:mm:ss is the date and time of entry.
The component_name is an abbreviation for the originating library server component. For example, ACSLM, ACSSA, CSI, storage server, etc.
The nn is the request ID enclosed in square brackets. This ID is generated by the ACSLM when it receives a valid request. You can enter a query request command to check the status of the request specified by the request ID.
The second and subsequent lines contain the following information:
The message_number is the number of the message.
The classification is a one-letter classification of the message. These classifications are as follows:
N - not classified
I - information only
W - warning
E - error
mod_id, mod_ver, and mod_line indicate respectively the file name of the ACSLS module that generated the message, the module version, and the module line number. These identifiers are included to help Oracle Support personnel isolate the cause of the problem. They are not intended to be used by system administrators or library users.
The function is the component function that generated the message. Error messages (E) generally include function. Informational messages (I) generally omit function. (See line three of the generic format for all entries, shown on the preceding page).
The message text is the message itself. The message may take up one or more lines of text.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Please use these websites to open a Service Request and report a problem or ask a question.
To begin, record the context in which a problem occurs or about which you have a question. Have the following information ready:
Release and maintenance level of ACSLS that's running
Hardware platform
Operating System (OS) release level
Library or libraries that ACSLS supports
What ACSLS was doing when the issue occurred
As part of the service call, Oracle Support may ask you to send the entire set of diagnostic logs and other diagnostic information for analysis. All of this data can be collected with a single command:
get_diags
Note:
You must be logged in as root to run get_diags.When this utility has collected all of the information, it prompts you to either email the data or to make it available for manual transfer.
If you elect to email the data directly from the ACSLS machine, make sure that email communication is possible between your ACSLS machine and the Internet. Your enterprise may have a firewall to prevent email going directly from the target machine. In this case, you can email the information to yourself within the enterprise and then forward the diagnostic data to Oracle.
Alternatively, you can elect to transfer the information manually. The get_diags utility advises you where to find the waiting tar packages for transfer. Typically, the staging area for diagnostic data is /export/backup/diag/acsss.
message text.
Explanation: An error occurred and is described by the message text variable.
Variable: The message text variable describes the error.
User Response: Resolve the error condition. If you need assistance, gather the information required and collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support. This error message may indicate a lost volume condition. For more information, see "Recovering Errant (Lost) Volumes" in "Troubleshooting" of the ACSLS Administrator's Guide.
unexpected status = status
Explanation: An ACSLS function received an unexpected status code from another ACSLS function.
Variable: The status variable is the code being passed between functions.
User Response: If the error recurs, gather the information required and collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
LSM lsm_id: Access door closed.
Explanation: The LMU has passed a message to ACSLS that indicates that the LSM access door was just closed.
Variable: The lsm_id variable is the LSM whose access door is closed.
User Response: None.
LSM lsm_id: Access door opened.
Explanation: The LMU has passed a message to ACSLS that indicates that the LSM access door was just opened.
Variable: The lsm_id is the LSM whose access door is open.
User Response: None.
ACS Identifier acs_id Invalid.
Explanation: The ACS identifier or variable is in the wrong format or has an invalid value.
Variable: The acs_id is the ACS identifier that is invalid.
User Response: Enter the correct format. See the "Component Types and Identifiers" in the "General Command Syntax" section of the "Command Reference" chapter in the ACSLS Administrator's Guide for the correct format for the ACS identifier.
LSM Identifier lsm_id Invalid.
Explanation: The LSM identifier or variable is in the wrong format or has an invalid value.
Variable: The lsm_id is the LSM identifier that is invalid.
User Response: Enter the correct format (see "Component Types and Identifiers" in the "General Command Syntax" section of the "Command Reference" chapter of the ACSLS Administrator's Guide) and the correct identifier value.
Invalid exit status returned from PID process-id.
Explanation: The exit status returned from the process ID (PID) was not considered a valid exit status.
Variable:
The status is the exit status returned from the process ID.
The process-id is the process ID value
User Response: Gather the information required and collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
LMU READY received for ACS Identifier acs_id.
Explanation: An LMU has been placed online.
Variable: The acs_id is the identifier of the ACS to which the LMU is connected.
User Response: None.
LSM NOT READY received for LSM Id lsm_id.
Explanation: The LSM has been taken offline.
Variable: The lsm_id is the identifier of the LSM that has gone offline.
User Response: None.
LSM READY received for LSM Identifier lsm_id.
Explanation: The LSM has been placed online.
Variable: The lsm_id is the identifier of the LSM that has gone online.
User Response: None.
PORT OFFLINE received for PORT Id port_id.
Explanation: A port between the server system and the LMU has been taken offline.
Variable: The port_id is the identifier of the port that has gone offline.
User Response: None.
cell cell_id - Reserved too long by another process
Explanation: A cell record in the database has been reserved by another process, and the audit is unable to access it after the appropriate number of retries and timeouts. The audit continues with the next cell. This error indicates that the system is under a heavy load.
Variable: The cell_id is the identifier of the cell record.
User Response:
Issue a query request all to see if there are any requests active for the cell. See the "Command Reference" chapter of the ACSLS Administrator's Guide for information on issuing commands.
If there are no requests active, issue an audit request for the subpanel containing the designated cell. See the "Command Reference" chapter.
If the problem persists, a software failure has occurred and the library server must be restarted. See the "Command Reference" chapter.
Cell cell_id - Missing cell detected
Explanation: The LSM robot is unable to locate a storage cell in the LSM. Possible causes are that the L-shaped target has been wiped off the cell or the cell carrier has detached from the LSM wall. This is a library configuration error and causes the library server to terminate.
Variable: The cell_id is the location of the missing cell.
User Response: The audit should be rerun after the error has been corrected and the library server has been re-initiated.
Panel panel_id - Audit of panel completed.
Explanation: For ACS, LSM, or server audits, this message is written to the Event Log for each panel that has been audited.
Variable The panel_id is the location of the panel that has been audited.
User Response: None.
Cell cell_id - routine_name returned unexposed status = status_code
Explanation: When a single cell is examined during an audit, an unexpected status was returned from a called routine. Audit terminates its examination of this cell.
Variable:
The cell_id is the cell being examined.
The routine_name is the routine that is examining information about the cell.
The status_code is the unexpected status code that was returned. Refer to the Status Codes chapter for the meaning of the status.
User Response: Issue a subpanel audit of just this cell, or examine the cell with SLConsole. If necessary, contact Oracle Support.
Cartridge vol_id found at location cell_id.
Explanation: A tape cartridge not listed in the database has been found in the ACS. The cartridge is added to the database.
Variable:
The vol_id is the external label of the tape cartridge.
The cell_id is the storage cell location where the cartridge was found.
User Response: None.
Cartridge vol_id, new location cell_id
Explanation: A tape cartridge is not in the location defined by the database. The cartridge is not moved in the ACS; instead, the database is updated to reflect the new storage location.
Variable:
The vol_id is the external label of the tape cartridge.
The cell_id is the assigned storage cell location of the cartridge.
User Response: None.
Cartridge vol_id not found.
Explanation: A tape cartridge listed in the database was not found in the ACS. The cartridge was removed from the database.
Variable: The vol_id is the external label of the tape cartridge.
User Response: None.
Unexpected Automatic Enter Request received: discarded.
Explanation: The CAP closed at a time when the request queue was empty. There was no matching request to which the CAP closure should be associated. The CAP closure is ignored.
User Response: Observe related event log messages for clues to the possible cause of this condition.
ACS acs_id configuration failed to verify.
Explanation: The ACS configuration in the library server database does not match the configuration defined in the LMU. Recovery processing terminates.
Variable: The acs_id is the unique identifier of the ACS.
User Response: After recovery processing terminates, rerun the library server acsss_config program to redefine the library configuration in the database.
Drive drive_id: Configuration failed to verify
Explanation: The recovery process was unable to successfully verify the drive configuration in the database against the configuration defined in the LMU. This condition may be because the LSM is offline or because there is an actual configuration mismatch.
Variable: The drive_id is the unique identifier of the drive.
User Response: Issue a query lsm request to display the state of the LSM. If it is online, you must run the acsss_config program to redefine the configuration in the library server database. Then:
Check the drive for any problems.
If there are drive problems, fix them.
Vary the drive and the LSM online.
If the problem persists, or if the drive is new or has been removed, run acsss_config. See the "Configuring your Library Hardware" chapter in the ACSLS Administrator's Guide for more information on procedures for reconfiguring ACSLS.
LSM lsm_id: configuration failed to verify.
Explanation: The LSM configuration in the database does not match the configuration defined in the LMU. Recovery processing terminates. This message will be followed by a Server system recovery failed message.
Variable: The lsm_id is the LSM whose configuration does not match that defined in the LMU.
User Response: Check previous Event Log entries for additional information about the failure. Follow the suggested action for the associated error message (or messages).
ACS acs_id: No ports online: marked offline.
Explanation: The server system is not able to communicate with any ports for the specified ACS. Recovery will continue, but the ACS and its LSMs are marked as offline in the database.
Variable: The acs_id is the ACS that was updated.
User Response: When recovery completes, do the following:
Vary the port online.
Does this correct the problem?
Yes - Vary the ACS online. The action is completed.
No - Follow the remaining steps in this procedure.
Find and fix any problem with the port. Among other conditions, check these:
The LMU is down.
A cable is missing or there is a bad connection.
The port is bad.
Vary the port online.
Vary the associated ACS(s) online.
Note:
If you have more than one ACS, repeat the steps above for each additional ACS.No server ports online.
Explanation: The server system is not able to communicate with any ACS. Recovery continues, but all ACSs and their LSMs are marked as offline.
User Response: To vary an ACS online, at least one communications port to the ACS must be online. When recovery completes, do the following:
Issue vary online requests to the appropriate port(s).
Vary all associated ACSs online.
Port port_id: Failed to go online: marked offline.
Explanation: The server system can not communicate with a port to an ACS. The port is marked offline in the database.
Variable: The port_id is the port that failed to go online.
User Response: Check the communications line between the server system and the LMU. If the line is intact, issue a vary online request for the designated port.
Cell cell_id: Corrected cell status to status
Explanation: The status of a cell record was updated based on ACSLS processing.
Variable:
The cell_id is the specific cell which was updated.
The status indicates the new status of the cell.
User Response: None. This is a notification only.
Drive drive_id: Corrected drive status to status
Explanation: The status of a drive record was updated based on ACSLS processing.
Variable:
The drive_id is the specific drive which was updated.
The status indicates the new status of the drive.
User Response: None. This is a notification only.
Volume vol_id: Corrected volume status to status.
Explanation: The status of a volume record was updated based on ACSLS processing.
Variable:
The vol_id is the specific volume which was updated.
The status indicates the new status of the volume.
User Response: None. This is a notification only.
LSM lsm_id: Hardware failed to vary offline/online: marked offline
Explanation: A request to vary an LSM offline was processed to completion, but the LSM failed to vary the LSM offline.
Variable: The lsm_id is the LSM in the request.
User Response: Run the library diagnostics to help isolate the cause of the problem (see the appropriate hardware maintenance manual for instructions). Gather the information required and collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
LSM lsm_id is full; volume vol_id cannot be recovered and is deleted.
Explanation: ACSLS found this volume in the playground or in-transit cell or in a PCP cell while recovering an LSM. It attempted to recover the volume by moving it to a new home cell in this LSM. However, the volume could not be recovered because the LSM was full. The volume was marked deleted in the database.
Variable:
The lsm_id identifies the LSM being recovered.
The vol_id identifies the deleted volume.
User Response:
Eject a volume from the LSM.
Vary the LSM offline and back online to recover the volume.
component component_id: Overridden by another vary request.
Explanation: The specified component was not varied to the specified state because the request was overridden by another vary request.
Variable:
The component is the library component (for example, ACS).
The component_id is the identifier of the library component.
User Response: None. If desired, resubmit the vary request.
File file: operation failed on \"%s\" (errno=error_no).
Explanation: An operation performed on an Event Log file failed.
Variable:
The file is the file on which the operation failed.
The operation is the operation that failed.
The error_no is the system error number associated with this file operation problem.
User Response: Gather the information required and collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Volume vol_id: Corrected volume type from media_type1 to media_type2 cartridge.
Explanation: An ACSLS audit detected a volume with an incorrect media type. The audit updated the ACSLS database with the correct volume media type.
Variable:
The vol_id is the volume ID.
The media_type1 is the incorrect volume media type.
The media_type2 is the corrected volume media type.
User Response: None.
surr_main (PID #####): Creating socket SURROGATE failed on "#####".
Explanation: The Surrogate main routine tried to create a socket (using the socket() system call) to listen for requests from the Library Management Gateway. Each Surrogate process that is running has its own unique socket. The systems' response is to use the acsss_daemon to abnormally terminate the IPC Surrogate and automatically restart ACSLS (up to 10 times).
Variable: The ##### is the process ID of the Surrogate trying to create a socket.
User Response:
Look for associated errors that may indicate why the socket() call failed.
Kill the ACSLS system using the kill.acsss command, then kill any additional "zombie" ACSLS processes (using ps | grep acs).
Restart ACSLS. It may be necessary to reboot the ACSLS host to release any hung sockets.
If the problem persists, check to see whether UNIX system limits have been exceeded on sockets, file descriptors, or other network resources.
If the problem continues, gather the information required and collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Volume vol_id: Locked volume deleted, lock was lock_id.
Explanation: A volume with a non-zero lock identifier was deleted.
Variable:
The vol_id is the volume identification.
The lock_id is the identifier of the lock.
User Response: None.
Timed out waiting for message.
Explanation: A process passed an internal request to another process. The latter did not respond within the designated timeout period.
User Response: Look at related event log messages for clues to the possible cause of this condition.
surr_main (PID #####): Environment variable SURROGATE_QUEUE_AGE is not defined or has a null value: exiting.
Explanation: The Surrogate main routine was unable to get the SURROGATE_QUEUE_AGE dynamic environment variable or the variable is not correctly set. The IPC Surrogate terminates.
Variable: The ##### is the process ID of the Surrogate issuing the error.
User Response: Define the SURROGATE_QUEUE_AGE variable with the acsss_config program.
surr_main (PID #####): Environment variable SURROGATE_TIMEOUT is not defined or has a null value: exiting
Explanation: The Surrogate main routine was unable to get the SURROGATE_TIMEOUT dynamic environment variable or the variable is not correctly set. The IPC Surrogate terminates.
Variable: The ##### is the process ID of the Surrogate issuing the error.
User Response: Define the SURROGATE_TIMEOUT variable with the acsss_config program.
surr_main (PID #####): Environment variable SURROGATE_PORT is not defined or has a null value: exiting.
Explanation: The Surrogate main routine was unable to get the SURROGATE_PORT dynamic environment variable or the variable is not correctly set. The IPC Surrogate terminates.
Variable: The ##### is the process ID of the Surrogate issuing the error.
User Response: Define the SURROGATE_PORT variable with the acsss_config program.
Unexpected ACSLH catalog status status detected.
Explanation: After a catalog request was issued by an ACSLS component, a response was received but contained a status code which was not expected by the requesting component.
Variable: The status is the specific status code.
User Response: None. Refer to the event log for additional information.
Unexpected message detected, IPC identifier is ipc_id
Explanation: An orphaned response is returned from one process to another that does not match any outstanding request.
Variable: The ipc_id is the identifier assigned to this message.
User Response: Observe related event log messages for clues to the possible cause of this condition.
Unexpected status status detected.
Explanation: An ACSLS function received an unexpected status code from another ACSLS function.
Variable: The status is the code being passed between functions.
User Response: Gather the information required and collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Volume vol_id Unknown media type detected.
Explanation: While performing Cartridge Recovery, a cartridge with a readable label was encountered for which no volume record was recorded in the database. In the process of adding a volume record, an attempt was made to determine volume type based on media type. That attempt failed because the media type was unknown.
Variable: The vol_id is the specific volume identifier of the cartridge.
User Response: None.
Removing file file: failed on cause of failure.
Explanation: An operation performed on an Event Log file failed.
Variable:
The file is the name of the event log file.
The cause of failure is the cause of the operation's failure.
User Response: Gather the information required and collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Unsupported version version packet detected: discarded.
Explanation: The ACSLS CSI detected an unsupported packet version on a request.
Variable: The version is the unsupported packet version.
User Response: Either update the client application to use a supported packet version or, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Volume vol_id: Found in cell/CAP/drive/recovery cell_id/CAP_id/drive_id/cell added.
Explanation: This message is issued when a misplaced tape is found in the library by vary or CAP processing.
Variable:
The vol_id is the identifier of the volume that was found.
The cell/CAP/drive/recovery is the location type where the volume was found.
The cell_id/CAP_id/drive_id/cell is the identifier of the location where the volume was found. In the case of a volume being found in the playground area (recovery), only the word cell, not the cell_id, is output.
User Response: None.
Misplaced cartridge detected; volume vol_id cannot be recovered and is deleted.
Explanation: ACSLS found this volume in the playground/in-transit cell or in a PCP cell while recovering an LSM. It attempted to recover the volume by moving it to a new home cell in this LSM. However, the move failed because the destination cell contained a cartridge. The volume has not been recovered and is marked deleted in the database.
Variable: The vol_id identifies the deleted volume.
User Response:
Check that the problem is not a single misplaced cartridge.
If not, audit the LSM to update the ACSLS database to match the actual contents of the library.
Vary the LSM offline and back online to recover the volume.
Volume vol_id: New home location is cell cell_id.
Explanation: When checking a storage cell, Cartridge Recovery encountered a cartridge that appeared to be misplaced. The recorded home cell for that cartridge was checked and found to be either empty or full with some other cartridge.
Variable:
The vol_id is the specific volume identifier of the cartridge.
The cell_id is the cell in which the cartridge was found.
User Response: None. The volume record for this cartridge is updated to reflect the new home cell location.
Audit started.
Explanation: Audit processing has begun.
User Response: None.
calling_routine:id_type indentifier called_routine() unexpected status = status_code.
Explanation: A routine in audit received a failing status from a called routine. The calling routine terminates with a failing status code.
Variable:
The calling_routine is the calling routine.
The id_type is the type of identifier (for example: lsm, cap, panel, subpanel).
The identifier is the component's identifier.
The called_routine is the called routine that returned the failing status code.
The status_code is the failing status code that was returned. Refer to the Status Codes chapter for the meaning of the status.
User Response: Earlier messages may explain the route cause of the failure. If necessary, contact Oracle Support.
Cartridge Recovery () unexpected status = STATUS_LIBRARY_NOT_AVAILABLE
Explanation: When checking storage cells, Cartridge Recovery was unable to check an LSM that was idle.
User Response: None.
audit completed not all cartridges were ejected, messages lost status = audit_completion_status.
Explanation: A spawned audit process has sent an incomplete or unintelligible message to the parent audit process. As a result, some errant cartridges may not be ejected.
Variable: The audit_completion_status is the status of the audit upon its completion.
User Response: To respond to this message, do the following:
Check previous Event Log entries to determine the reason for the lost message(s).
If the audit_completion_status is Audit cancelled or Audit failed, the audit should be rerun.
If the audit continues to fail, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Audit completed.
Explanation: Audit processing has completed successfully.
User Response: None.
audit cancelled not all cartridges were ejected, messages lost status = audit_completion_status.
Explanation: A spawned audit process has sent an incomplete or unintelligible message to the parent audit process. As a result, some errant cartridges may not be ejected.
Variable: The audit_completion_status is the status of the audit upon its completion.
User Response:
Check previous Event Log entries to determine the reason for the lost message(s).
If the audit_completion_status is Audit cancelled or Audit failed, the audit should be rerun.
If the audit continues to fail, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
If the audit_completion_status is Audit complete, no action is required, as the audit has completed successfully.
Audit cancelled.
Explanation: Audit processing has been cancelled. The database may have discrepancies or errant cartridges may not have been ejected.
User Response: None.
Audit failed not all cartridges were ejected, messages loststatus = audit_completion_status.
Explanation: A spawned audit process has sent an incomplete or unintelligible message to the parent audit process. As a result, some errant cartridges may not be ejected.
Variable: The audit_completion_status is the status returned by the audit.
User Response: To respond to this message, do the following:
Check previous Event Log entries to determine the reason for the lost message(s).
If the audit_completion_status is Audit cancelled or Audit failed, the audit should be rerun.
If the audit continues to fail, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
If the audit_completion_status is Audit complete, no action is required, as the audit has completed successfully.
Audit failed.
Explanation: Audit processing has terminated due to some error condition. The description of the error is displayed in the Command Area. The database may have discrepancies or errant cartridges may not have been ejected.
User Response: Check previous Event Log entries to determine the cause of the failure. Follow the suggested action for the associated message(s). Once this is done, rerun the audit.
Audit failed not all cartridges were ejected, status = status
Explanation: An ACSLS audit was interrupted (for example, by an idle force command or a hardware failure).
Variable: The status describes the event that interrupted the audit.
User Response: Resubmit the audit.
Lock request size incorrect.Req = string1, Exp = number1, Rec = number2.
Explanation: The size of the lock request submitted does not match the expected byte count.
Variable:
The string1 is the current type of lock request.
The number1 is the expected byte count of the current lock request.
The number2 is the actual byte count of the current lock request.
User Response: Re-submit the lock request with the correct information in the request.
Initiation started, acsss_version.
Explanation: Library server initiation has begun.
Variable: The acsss_version is the ACSLS version number.
User Response: None.
Initiation completed (library server).
Explanation: Product initiation completed successfully.
User Response: None.
wait() return invalid PID PID
Explanation: The PID returned by wait is not the expected PID.
Variable: The PID is the process ID returned by wait().
User Response: Restart ACSLS, if needed. If restarting ACSLS fails after three tries, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
exit status (status_code), status, received from process_name
Explanation: The library server daemon has received an unexpected exit status from a library server process.
Variable:
The status_code is the library server status code that was generated as a result of the exit.
The status is the numeric exit status from the process.
The process_name is the library server process.
User Response: If this error occurs when not shutting down ACSLS or issuing an idle force command, check the following conditions:
Processing continues, no more errors.
No action. Message informational only.
Processing continues but the same error continues over a period of days, weeks, or months.
Collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Processing does not continue.
Collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
signal (signal_num) terminated process_name.
Explanation: An ACSLS process died from the specified signal. ACSLS will either restart the process or terminate depending on which process terminated. This message is informational only if it was received when shutting down ACSLS.
Variable:
The signal_num is the signal number received that terminated the process.
The process_name is the library server process that terminated.
User Response: Restart ACSLS, if needed. If restarting ACSLS fails after three tries, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Termination invoked, termination_status.
Explanation: Library server termination has begun.
Variable: The termination_status is the library server status code which indicates the reason for the termination
User Response: Follow the suggested action for the appropriate termination_status:
If termination_status is STATUS_TERMINATED, there is no action, as this indicates a manually invoked termination of the software by the acsss user.
If termination_status is STATUS_DATABASE_ERROR, use the following procedure:
Attempt to restart the library server software with the rc.acsss command file.
You may be prompted for the acsss user password. If you are acsss or root, you are not prompted.
Did the library server restart successfully?
Yes - go to step 3.
No - go to step 4.
Run the database recovery utility, rdb.acsss (as the acsss user).
The rdb.acsss command prompts you to enter a tape. Enter the most recent backup tape you have, since this utility writes over your existing database. (If you do not have a current backup tape, enter Control+c to quit out of this procedure.)
When rdb.acsss completes successfully, attempt to restart the library server software with the rc.acsss utility.
Perform an audit to reconcile the database with the physical contents of the library.
If none of the above steps are successful, collect relevant ACSLS data.
If termination_status is STATUS_CONFIGURATION_ ERROR, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support. They adjust the LMU configuration to make it match the physical configuration of the library. Once this has been done, rerun the library server configuration program to redefine the library configuration in the database.
If termination_status is STATUS_RECOVERY_FAILED, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
wait failed, ret = wait_return_code, errno = error_no.
Explanation: The UNIX system call wait() failed.
Variable:
The wait_return_code is the code returned by the wait.
The error_no is the system error number.
User Response: Restart ACSLS if needed. If restarting ACSLS fails after three tries, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
process_name restarted, pid process_id.
Explanation: A library server process has been automatically restarted.
Variable:
The process_name is the library server process that was terminated.
The process_id is the library server process identifier.
User Response: If this message recurs over a period of days, weeks, or months, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Unreadable Label cell_id.
Explanation: The robot was unable to decipher the external label of the volume.
Variable: The cell_id is the storage cell location where the volume resides.
User Response: Eject the volume and inspect the label. If you cannot determine which volume to eject, submit the following command:
sql.sh "select volid from volumetable where acs=v and lsm=w and panel=x and row=y and column=z."
In this example v, w, x, y, and z are the corresponding values for acs, lsm, panel, row, and column.
If this error occurs frequently with good labels, contact your Customer Service Engineer (CSE) to inspect the robotic vision system.
Destination location full: cell_id/drive_id
Explanation: The storage cell to which a cartridge was to be dismounted is full although the database indicates it is empty. The robot will retry the dismount until it finds an available cell. The most likely cause for this error is that someone entered the LSM and moved a cartridge manually.
Variable:
The cell_id is the storage cell location indicated in the database.
The drive_id is the identifier of the tape drive.
User Response: You should perform an audit on the LSM to reconcile the database with the physical contents of the LSM.
Source location empty: cell_id
Explanation: A cartridge marked for ejection was not found in its storage cell when the robot went to move it to the CAP. The audit terminates. This error is most likely the result of a hardware failure in the robot.
Variable: The cell_id is the identifier of the cell where the cartridge marked for ejection should have been.
User Response: Check previous entries in the Event Log for additional information about the error. Use the proper LSM entry procedure and check the robot's hands for in-transit cartridges; remove any cartridges that you find there. Repeat the audit after varying the LSM back online.
Drive drive_id: No cleaning cartridge available
Explanation: The specified drive requires cleaning but no cleaning cartridges are available. The mount proceeds.
Variable: The drive_id is the identifier of the tape drive.
User Response: Add more cleaning cartridges, making sure these are compatible with the drive type. See "Defining Cleaning Cartridges" in the "Cleaning Transports" section of the "Cartridge Management" chapter of the ACSLS Administrator's Guide for information about adding cleaning cartridges.
mc_mo_error: Cleaning failed. Drive drive_id
Explanation: The mount operation involving a cleaning cartridge failed.
Variable: The drive_id is the identifier of the drive requesting the cleaning operation.
User Response: Observe the associated error messages in the event log to determine the root cause of the failure.
Cleaning cartridge vol_id: Usage limit exceeded.
Explanation: Cleaning a tape drive has caused a cleaning cartridge to exceed its specified maximum usage. The cleaning cartridge is no longer available for automatic cleaning selection.
Variable: The vol_id is the identifier of the cleaning cartridge.
User Response: Eject the cleaning cartridge.
Source location empty: cell_id
Explanation: The LSM robot was unable to find the tape cartridge in the location indicated by the database. The request fails.
Variable: The cell_id is the storage cell location indicated in the database.
User Response: The most likely cause for this error is that someone entered the LSM and moved the cartridge manually. You should perform an audit on the LSM to reconcile the database with the physical contents of the library.
Cartridge in cell_id, unreadable label
Explanation: The LSM robot was unable to read the label of the cartridge found in the specified drive. The request fails.
Variable: The cell_id is the storage cell location indicated in the database.
User Response: Eject the cartridge. Correct the label problem and re-enter the cartridge.
Volume record created for vol_id
Explanation: A cell or drive marked reserved is found to contain a tape cartridge that does not exist in the database. A record is created for the new volume. This message usually appears together with the drive (drive_id) readable, marked in use message.
Variable: The vol_id is the volume record that was created.
User Response: We recommend that you perform an audit of the LSM to reconcile the database with the physical contents of the library.
Table lookup failure m_id: m_id
Explanation: A message processing error occurred for a mount request. The mount is identified as incomplete due to some failure.
Variable: The m_id is the mount request ID.
User Response: If the error recurs, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Volume: vol_id may be jammed in drive: drive_id
Explanation: The specified volume is jammed in the specified transport.
Variable:
The vol_id is the jammed volume.
The drive_id is the drive that contains the jammed volume.
User Response: The jammed volume must be manually unloaded from the drive; if necessary, contact Oracle Support.
Cartridge vol_id, new location cell_id.
Explanation: This message reports the recording of a new location for the cartridge in the ACSLS database.
Variable:
The vol_id is the volume identifier of the volume that was moved.
The cell_id is the new location of the moved volume.
User Response: None.
volume vol_id not in drive drive_id, deleted.
Explanation: A drive marked as containing a tape cartridge is found to be empty. The volume record is deleted from the database.
Variable:
The vol_id is the volume record that was deleted.
The drive_id is the tape drive that the database indicated contained the cartridge.
User Response: We recommend that you perform an audit of the LSM to reconcile the database with the physical contents of the library.
Unknown packet received, command command, identifier ipc_id
Explanation: The ACSSA has received a message packet with an IPC identifier not found in the request queue. The ACSSA is unable to process the message.
Variable:
The command is the entry in the MESSAGE_HEADER.
The ipc_id is the identifier assigned to this message (used to synchronize requests and responses).
User Response: If the message occurs frequently, use the following procedure to shut down and restart the library server software at your earliest convenience:
From a Command Processor window, issue an idle request to place the library server in a quiescent state.
Login as the acsss user, and shut down the library server using the kill.acsss utility.
Restart the library server using the rc.acsss utility.
cl_ipc_read() byte count < sizeof(REQUEST_HEADER) = bytes
Explanation: An internal ACSLS failure occurred.
Variable: The bytes is the number of bytes read before the failure.
User Response: If the error recurs, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
ipc_read: shared_block_read failed, errno = error_no
Explanation: An internal ACSLS failure occurred.
Variable: The error_no describes the failure.
User Response: If the error recurs, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
cl_ipc_read: accept() failed, errno + error_no.
Explanation: While establishing communication between ACSLS processes, the receiving side was unable to accept an incoming connection from the sending side.
Variable: The error_no is the error code returned from the system call to accept().
User Response: None. Additional messages in the Event Log may report a failure in inter-process communication (IPC).If the error recurs, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
cl_ipc_read: invalid byte_count detected.
Explanation: A packet that appeared to contain invalid data was received during communication between ACSLS processes.
Variable: None.
User Response: None. Additional messages in the Event Log may report a failure in inter-process communication (IPC). If the error recurs, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Invalid type type identifier.
Explanation: The type identifier is in the wrong format or has an invalid value.
Variable: The type identifier refers to an invalid type of identifier used by the operator across the network or ACSLS.
User Response: Enter the correct format (see "Component Types and Identifiers" in the "General Command Syntax" section in the Command Reference" chapter of the ACSLS Administrator's Guide) and/or the correct identifier value.
Invalid tag count file=number1 vs. code=number2.
Explanation: An incorrect number of entries was found in the dynamic variables file.
Variable:
The number1 is the number of entries found in the file.
The number2 is the number of entries expected by ACSLS.
User Response:
Log in as acsss.
Run: dv_print > filename.
Save the dynamic variables file for Oracle Support.
Collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
cl_ipc_read: read() failed, errno = error_no.
Explanation: The receiving side was unable to successfully read input from the sending side during communication between ACSLS processes.
Variable: The error_no is the error code returned from the system call to read().
User Response: None. Additional messages in the Event Log may report a failure in inter-process communication (IPC). If this problem recurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
LH error type = status.
Explanation: This message indicates that ACSLS has received an abnormal status code from the library hardware.
Variable: The status is the code being passed between functions.
User Response: Observe the accompanying LH error type to determine the root cause of this message.
EXEC SQL Lock timeout: insert into acstable * values (acs, partition_id, acs_state acs_desired_state).
Explanation: An attempt to insert records into the table failed.
Variable:
The acs is the ACS identifier.
The partition_id is the partition ID of the ACS.
The acs_state is the actual state of the ACS.
The acs_desired_state is the state you want for the ACS.
User Response:
Restart ACSLS.
If the problem persists, restart the database server.
EXEC SQL Error on insert into acstable * values (acs, partition_id, acs_state acs_desired_state).
Explanation: An attempt to insert records into the table failed.
Variable:
The acs is the ACS identifier.
The partition_id is the partition ID of the ACS.
The acs_state is the actual state of the ACS.
The acs_desired_state is the state you want for the ACS.
User Response:
Restart ACSLS.
If the problem persists, restart the database server.
EXEC SQL select from lsmtable where LSM = lsm_no and di_status = :di_status
Explanation: An unexpected error while reading from the ACSLS database.
Variable:
The lsm_no is the LSM number included in the failing operation.
The di_status is the status returned by the database interface.
User Response: See ACSLS Database log files. If you need assistance, gather the information required, described above, and collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
EXEC SQL unable to delete volume vol_id because of database error.
Explanation: ACSLS could not find a volume in the library and attempted to mark it deleted, but the ACSLS database interface returned an unusual status to the volumetable update. The database update failed.
Variable: The vol_id identifies the absent volume.
User Response:
Stop ACSLS (kill.acsss).
Stop the database (db_command stop).
Kill any hanging ACSLS processes.
Restart ACSLS (one time).
If the problem persists, you need the help of support to verify that the table volumetable exists and that the "acsss" user has the proper permissions to update it. Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support".) Then contact Oracle Support.
byte count(byte_count) too small for min packet size(min_size) ignored.
Explanation: The ACSLM has received a message that is too small from a CSI or the ACSSA. The ACSLM did not attempt to interpret the message because it did not have enough information. This could be a problem with either the network or the software.
Variable:
The byte_count is the number of bytes in the message.
The min_size is the minimum size of a valid, readable message.
User Response:
Make sure the problem is not caused by the network or an ACSAPI client.
If the problem is not a network or ACSAPI client problem collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support".) Then contact Oracle Support.
Severe Error (status), Exiting to ACSSS.
Explanation: The ACSLM has encountered a fatal error, such as a database failure or an inconsistency in the library configuration. The ACSLM will automatically initiate recovery processing if it is able. If recovery fails, and if you determine that the problem is not being caused by your network or by your ACS API client software, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support".). Then contact Oracle Support. If recovery completes with a recovery incomplete status, there is no need to call; however, you should audit the libraries at your earliest convenience.
Variable: The status is a message indicating the nature of the severe error.
User Response: Check previous Event Log entries to determine the cause of the failure. Follow the suggested action for the associated message(s).
Drive drive_id lookup failed
Explanation: While performing Cartridge Recovery, a volume record was encountered with a status that indicated a drive association (such as in drive, mount or dismount activity). No record was found in the database for the drive that was recorded in the volume record.
Variable: The drive_id is the specific drive identifier that was recorded in the volume record.
User Response: None. Cartridge Recovery proceeds as if no drive were recorded for the volume.
XDR message translation failure.
Explanation: During a translation of a packet of data from one version (1, 2, 3, or 4 packet) to another version, the XDR (external data representation) translator detected an error.
Variable: None.
User Response:
Reboot the server system and see if the problem persists.
If it does, contact Oracle Support with a CSI trace during the failure and the full event log during the CSI tracing.
Initiation Started.
Explanation: CSI initiation has been started.
Variable: None.
User Response: None.
Creation of connect queue failed.
Explanation: The call to the cl_qm_init() or cl_qm_create() common library function has failed while trying to create the internal SSI address connection queue.
Variable: None.
User Response:
From a Command Processor window, issue an idle request to place the library server in a quiescent state.
Login as the acsss user, and shut down the library server using the kill.acsss utility.
Restart the library server using the rc.acsss utility.
If the error recurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Creation of network output queue failed
Explanation: The CSI was unable to create the network output queue which is used for messages between the CSI and the SSI.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Initiation completed.
Explanation: The specified process has completed initiation procedures.
Variable: None.
User Response: None.
Undefined message detected: discarded.
Explanation: The CSI has encountered a message from the ACSLM or the Network Interface (NI) that cannot be delivered because of incorrect message format or a CSI failure. The message is discarded.
Variable: None.
User Response: If the error recurs, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Cannot delete Q-id queue_id, Member: member_id.
Explanation: The CSI is unable to delete a message in an internal queue.
Variable:
The queue_id is the identifier of the CSI connection queue.
The member_id is the identifier of the queue member it is trying to delete.
User Response: If the error recurs, collect relevant ACSLS data. Refer to "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Invalid communications service.
Explanation: This entry may indicate that neither environment variable for the two available communication services has been defined. These variables are CSI_TCP_RPCSERVICE and CSI_UDP_RPCSERVICE, which can be defined through acsss_config. See the "Configuring Your Library Hardware" chapter in the ACSLS Administrator's Guide for information about using acsss_config. This message may also indicate that a request received from the SSI has incorrect values specified in the protocol-dependent portions of the CSI_HEADER.
Variable:
CSI_TCP_RPCSERVICE is the TCP communication service variable.
CSI_UDP_RPCSERVICE is the UDP communication service variable.
The acsss_config is the program used to configure your ACSLS environment.
CSI_HEADER is the variable that specifies CSI protocols and values.
User Response:
Make sure that your communication service has been defined using acsss_config.
If the problem still occurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Cannot send message message: discarded.
Explanation: The CSI is unable to communicate with a client. The CSI discards the message after the appropriate number of retries with timeouts.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Cannot get queue status Errno: error_no Q-id: queue_id, Member: member_id.
Explanation: The CSI is unable to get status information.
Variable:
The error_no is the system error number.
The queue_id is the identifier of the CSI connection queue.
The member_id is the identifier of the queue member for which the CSI is seeking status information.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Queue cleanup Q-id: queue_id, Member: member_id removed.
Explanation: The CSI has begun the process of purging old processes from its connection queue. The CSI routinely searches for processes older than CSI_CONNECT_AGETIME and purges them.
Variable:
The queue_id is the identifier of the CSI connection queue.
The member_id is the identifier of the queue member it is trying to delete.
User Response: None.
Cannot locate queue Q-id: queue_id, Member: member_id
Explanation: The CSI is unable to find a specific member in an internal queue.
Variable:
The queue_id is the identifier of the CSI connection queue.
The member_id is the identifier of the queue member it is trying to locate.
User Response: No action is required if the queue member is dropped because it is older than the connection queue aging time (defined by the CSI_CONNECT_AGETIME environment variable). If this error occurs before connection queue aging time has elapsed, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Queue creation failure.
Explanation: The CSI is unable to create its connection queue.
Variable: None.
User Response:
Restart ACSLS.
If this error occurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Cannot add member to queue Q-id: queue_id
Explanation: The CSI was unable to put a client's return address on its queue.
Variable: The queue_id is the identifier of the CSI connection queue.
User Response: If this error occurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Invalid procedure number.
Explanation: A program is trying to use the CSI, but the program is not using one of the two valid procedure numbers. This is a programming error in the client application.
Variable: None.
User Response: If this error occurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Unsupported module type module_type detected:discarded.
Explanation: The ACSLM detected a request with an IPC_HEADER module_type not set to TYPE_CSI or TYPE_SA. The ACSLM will only process requests received from a client application through the CSI, or from a user through the ACSSA.
Variable: The module_type is the invalid entry.
User Response: If this error occurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
RPC TCP client connection failed, rpc_error_msg Errno = error_no Remote Internet address: Internet_add, Port: port_id.
Explanation: The attempted TCP connection is not possible. This is an error in the client system network.
Variable:
The rpc_error_msg is a detailed error message generated by the RPC service itself. In most cases, this message will be Program number not registered, which indicates that either the CSI or the SSI is not running.
The error_no is the system error number.
The Internet_add is the address of the client machine to which the reply is sent.
The port_id is the port identifier.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
RPC_UDP client connection failed, rpc_error_msg, Remote Internet address: Internet_add, Port: port.
Explanation: The attempted UDP connection is not possible.
Variable:
The rpc_error_msg is a detailed error message generated by the RPC service itself. In most cases, this message will be Program number not registered, which indicates that the CSI or SSI is not running.
Internet_add is the address of the client host, expressed as an unsigned long integer.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Invalid network protocol.
Explanation: An unsupported network protocol has been passed. This is a programming error in the client SSI.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Cannot reply to RPC message.
Explanation: The CSI is unable to reply to an RPC message because the call to the svc_sendreply() function failed. This is an error in the client system network.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Unmapped previously registered RPC service.
Explanation: The CSI has been initiated. It notifies you that an RPC number previously assigned to the CSI still exists. The CSI un-maps this number and svctcp_create() remaps to a new one as a part of the initiation.
Variable: None.
User Response: None.
Create of RPC TCP service failed.
Explanation: The RPC call to the svctcp_create() function has failed.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Can't register RPC TCP service.
Explanation: The call to the svc_register() function failed.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Create of RPC UDP service failed.
Explanation: The RPC call to the svctcp_create() function failed.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Cannot register RPC UDP service.
Explanation: The call to the svc_register() function failed.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Termination Started.
Explanation: CSI termination has been started.
Variable: None.
User Response: None.
Termination Completed.
Explanation: CSI termination has been completed successfully.
Variable: None.
User Response: None.
LH error type = LH_ERR_TRANSPORT_BUSY drive_id
Explanation: The identified drive is busy.
Variable: The drive_id identifies the busy drive.
User Response: None.
Invalid command.
Explanation: The CSI received a request packet from the SSI with an unrecognizable command specified in the MESSAGE_HEADER portion of the CSI_REQUEST_HEADER.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Invalid location type.
Explanation: The CSI received a request packet from the SSI with an unrecognizable type specified in the message_data portion of the request.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Invalid type
Explanation: The CSI received a packet from the NI with either an unrecognizable TYPE in the IPC_HEADER portion of the CSI_REQUEST_HEADER or an unrecognizable IDENTIFIER type in the message packet.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Cannot read message from ACSLM: discarded.
Explanation: The CSI detected a message from the ACSLM but is unable to read it.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Operating system error error_no.
Explanation: The CSI encountered an operating system error. This message is indicative of a problem with the operating system itself, not with the CSI or the library server.
Variable: The error_no is the system error number; see your Oracle OS documentation for a description.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Duplicate packet from ACSLM detected:discarded.
Explanation: The CSI has received a duplicate IPC packet. It automatically drops the duplicate packet.
Variable: None.
User Response: If the error recurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Insufficient packet size = bytes.
Explanation: An internal ACSLS failure occurred.
Variable: The bytes is the packet size.
User Response: If the error recurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
line line_number, Unknown packet received, command = command.
Explanation: The ACSLM (library manager process) has received an unexpected IPC packet from another ACSLS process. This typically occurs when commands are cancelled because an outstanding request process (associated with the command) may still send packets back to the ACSLM before the request command is completely cleaned up.
Variable:
The line_number is the location in the ACSLS code where the error was detected.
The command is the type of ACSLS command packet received.
User Response: None.
CAP cap_id: Enter succeeded status.
Explanation: An enter operation was successful.
Variable:
The cap_id is the identifier of the CAP.
The status is the final status code of the enter command.
User Response: None.
Initiation of CSI Failed
Explanation: CSI initiation failed.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Cannot send message to NI:discarded, failure_msg. Errno = error_no (none) Remote Internet address: Internet_add Port: port_id.
Explanation: The NI's communications mechanism is unable to accept a message from the CSI. The CSI discards the message after the appropriate number of retries with timeouts.
Variable:
The failure_msg is the message text identifying the cause of the failure.
The error_no is the system error number.
Internet_add is the address of the client host, expressed as an unsigned long integer.
The port_id is the port identifier.
User Response: See the corresponding failure_msg description for an explanation and suggested action. Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Cannot send message to NI:discarded status Errno = error_no Remote Internet Address: Internet_add Port: port_id.
Explanation: The ACSLS server was unable to reply to a client, and has exhausted its retry attempts. The reply packet will be discarded.
Variable:
The status is the final status code of the function.
The error_no is the system error number associated with the failure (which may not be meaningful to the ACSLS error).
The Internet_add is the address of the client machine to which the reply is sent.
The port_id is the client machine port to which the reply is sent.
User Response: If client/server communications and requests are not being affected, no action is necessary. If those communications/requests are being adversely affected, Oracle recommends that you do the following:
Have your network personnel determine if either the local net or traffic on that net is causing the problem.
If the local net is not the cause, contact your client system software provider for help in determining why the client is not accepting response packets from the server.
Unexpected signal caught, value: signal.
Explanation: The CSI received a signal that it did not expect.
Variable: The signal is the signal value that the CSI has received.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Dropping from Queue: Remote Internet Address: Internet_add Port: port_id ssi_identifier: ssid Protocol: protocol_type Connect type: connection_type
Explanation: The ACSLS server was unable to reply to a client, and has exhausted its retry attempts. The reply packet will be discarded.
Variable:
Internet_add is the address of the client machine to which the reply is sent.
The port_id is the client machine port to which the reply is sent.
The ssid is the identifier associated with the client-side network interface.
The protocol_type is the network protocol being used.
The connection_type is the network connect type.
User Response: If client/server communications and requests are not being affected, no action is necessary. If those communications/requests are being adversely affected, Oracle recommends that you do the following:
Have your network personnel determine if either the local net or traffic on that net is causing the problem.
If the local net is not the cause, contact your client system software provider for help in determining why the client is not accepting response packets from the server.
Volume vol_id missing, home cell was cell_id, drive was drive_id, unable to examine.
Explanation: This tape cartridge was not found where ACSLS expected it, but either the home cell or the drive couldn't be examined during the recovery process. The volume record will remain in the database until ACSLS can examine all recorded locations for the cartridge and determine that it is not in any of these locations.
Variable:
The vol_id is the volume identifier of the missing cartridge.
The cell_id is the storage cell location for this cartridge recorded in the database.
The drive_id is the tape drive containing the cartridge, as recorded in the database, or none.
User Response: No action is required. The cartridge is recorded as being in a home cell or a drive that cannot be examined now. ACSLS will attempt to recover the cartridge when the LSM comes online or the drive is ready and communicating with the library. If ACSLS does not find the cartridge, the customer may perform an audit of the ACS to locate lost volumes.
Volume vol_id was not found and will be deleted.
Explanation: This tape cartridge's volume record is deleted from the database.
Variable: The vol_id is the volume identifier of the missing cartridge.
User Response: No action is required.
Volume vol_id deleted, home cell was cell_id, drive was drive_id
Explanation: This tape cartridge's volume record is deleted from the database
Variable:
The vol_id is the volume identifier of the missing cartridge.
The cell_id is the storage cell location for this cartridge recorded in the database.
The drive_id is the tape drive containing this cartridge, as recorded in the database, or none.
User Response: No action is required. The customer may perform an audit of the ACS to locate lost volumes.
ACS: acs_id port: port_id Parity error.
Explanation: A parity error occurred in communications between the ACSLS server and the LMU.
Variable:
The acs_id is the ACS identifier.
The port_id is the identifier of the ACSLS-to-LMU port.
User Response: None. If this message recurs often or is adversely affecting completion of library requests, check the ACSLS-to-LMU cable connection.
ACS: acs_id port: port_id Read timed out.
Explanation: A read timed out in communications between the ACSLS server and the LMU.
Variable:
The acs_id is the ACS identifier.
The port_id is the identifier of the ACSLS-to-LMU port.
User Response: None. If this message recurs often or is adversely affecting completion of library requests, check the ACSLS-to-LMU cable connection.
ACS: acs_id No queue entry found.
Explanation: This message indicates that a response was received from the LMU with error status but when ACSLS searched its work queue for the corresponding entry it could not find it. The actual cause is not determinable in this instance but could be as a result of data transmission error between the LMU and ACSLS or possibly a duplicate return message from the LMU.
Variable: The acs_id is the ACS identifier.
User Response: If the problem recurs, check the LMU logs for any hardware problems, and if necessary, obtain an LMU trace to aid your hardware service representative in diagnosing the problem.
ACS: acs_id Unexpected acknowledge received from the library; ignored.
Explanation: The ACSLS Library Handler received an unexpected acknowledgement from the library. This extra acknowledgement was ignored.
Background: When ACSLS communicates with a library using the Host/Library Interface (HLI), each transmission must be acknowledged. If an acknowledgement is not received with 10 seconds, ACSLS sends the transmission again. If ACSLS then receives the delayed acknowledgement, it is ignored. HLI libraries include the SL8500 and SL3000.
Variable: The acs_id is the ACS identifier.
User Response: None. ACSLS and the library automatically re-send transmissions that are not acknowledged within the time-out period.
Invalid character received, line = line_number.
Explanation: A data packet received from the LMU contains an invalid character. Valid characters are A:Z and 0:9.
Variable: The line_number is the location in the ACSLS code where the error was detected.
User Response: If the problem persists and the system does not recover, check cable connections between the LMU and the ACSLS server.
ACS: acs_id port: port_id Failed to connect, line = line_number
Explanation: A connection between the ACSLS server and the LMU failed to establish communications.
Variable:
The acs_id is the ACS identifier.
The port_id is the identifier of the ACSLS-to-LMU port.
The line_number is the location in the ACSLS code where the error was detected.
User Response: Check the physical connection and cable between the specified port on the ACSLS server and the LMU.
Rp error: Co_4400:Vwrite: ACS acs_id: No connection created yet, line = line_nbr.
Explanation: An ACSLS request process attempted to send a request to the library when ACSLS did not have an active connection to the library.
Variable:
The acs_id identifies the library (ACS) to which ACSLS tried to send the request.
The line_nbr identifies the line of source code that issued the message.
User Response: Before sending requests to the library, restore communication between ACSLS and the library:
Ensure that the library is ready.
The desired state of both the port(s) and ACS must be online. If they are not online, vary them online.
Resolve any network communications issues between ACSLS and the library.
ACS: acs_id port: port_id Resetting port, line = line_number.
Explanation: A communications error occurred between the ACSLS server and the LMU. The port is being reset to attempt to retry communications.
Variable:
The acs_id is the ACS identifier.
The port_id is the identifier of the ACSLS-to-LMU port.
The line_number is the location in the ACSLS code where the error was detected.
User Response: None, if communications are successfully reestablished. If not, check the physical connections between the ACSLS server and the LMU, as well as the acsss_config setting of the ACS communications port.
LC/LMU error: Co_cap_opened_1: CAP acs_id,lsm_id,cap_id, Duplicate unsolicited message received, line=line_number.
Explanation: The ACSLS library handler received an unexpected response from the specified cap. The current cap operation will be retried.
Variable: None.
The acs_id is the ACS identifier.
The lsm_id is the LSM identifier.
The cap_id is the CAP identifier.
The line_number is the location in the ACSLS code where the error was detected.
User Response: None, if the error occurs frequently, then check the specified cap for a misaligned magazine, cartridge, or obstruction.
Invalid or unknown media type found in transaction. Unpack LMU Message Transaction.
Explanation: The LMU encountered an unknown or invalid media type associated with the object volume of the current library operation.
Variable: None.
User Response: Check the media type character on the physical label of the associated volume. If the media type character is garbled or missing, a new label should be attached to the volume. Multiple instances of this error may point to problems with the robotics vision system.
Volume vol_id: Found in cell/CAP/drive/recovery cell_id/CAP_id/drive_id/cell action.
Explanation: This message is issued when a misplaced tape is found in the library.
Variable:
The vol_id is the identifier of the volume that was found.
The cell/CAP/drive/recovery is the location type where the volume was found.
The cell_id/CAP_id/drive_id/cell is the identifier of the location where the volume was found. In the case of a volume being found in the playground area (recovery), only the word cell, not the cell_id, is output.
The action is either added if a volume record was created for it or recovered if this volume already had a volume record.
User Response: None.
DBMS error. SQL Code (sql_code), Return Code (return_code) and message (error_message). DI_STATUS = di_status.
Explanation: ACSLS database found an invalid transaction or a system error.
Variable:
The sql_code is the SQL error code returned by ODBC.
The return_code is the value returned by the database operation.
The error_message is the description of the sql_code_code.
The di_status is the status returned by the database interface.
User Response: Resolve the error condition; if you need assistance, gather the information required, described above, and collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
LSM lsm_id offline.
Explanation: The LSM is offline, and is therefore unavailable for entering tape cartridges. If this message is logged during enter processing, the message means that the LSM was varied offline with the force option, while its CAP was being used for the enter.
Variable: The lsm_id is the identifier of the LSM.
User Response: Vary the LSM online and then reissue the enter request.
Transport failure drive_id.
Explanation: A hardware failure occurred in the specified transport.
Variable: The drive_id is the transport that failed.
User Response: Contact Oracle Support.
Server system idle.
Explanation: The ACSLM has been placed in the idle state by an operator and is unavailable for requests using library resources.
Variable: None.
User Response: None.
Server system running.
Explanation: The ACSLM has been placed in the run state.
Variable: None.
User Response: None.
CAP cap_id: Cartridges detected in CAP.
Explanation: Cartridges were detected in the CAP during a vary online operation or during library server initiation or recovery.
Variable: The cap_id is the identifier of the CAP.
User Response: Issue an enter request to unlock the designated CAP, then remove the cartridges from the CAP.
Drive drive_id: Clean drive.
Explanation: The specified drive needs to be cleaned.
Variable: The drive_id is the identifier of the library drive.
User Response: If Auto Clean is FALSE, mount a cleaning cartridge in the designated drive. If Auto Clean is TRUE, this message is informational only; the drive will be cleaned automatically prior to the next mount of the drive.
Library configuration error.
Explanation: The library configuration specified in the database is not the same as the one defined in the LMU, or a component appears in the database, but fails to respond to LMU commands. This error causes the library server to terminate.
Variable: None.
User Response: Rerun acsss_config. Then run an audit. See the "Configuring Your Library Hardware" chapter in the ACSLS Administrator's Guide for information about acsss_config and running an audit.
Database failure.
Explanation: An ACSLS process is unable to access the database. A database error code, indicating the reason for the failure, will also be written to the Event Log.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Event log is full.
Explanation: The Event Log has reached the maximum size defined in the library server installation. Messages will continue to be added to the Event Log, but this message will be logged at one-minute intervals until you reduce the size of the log.
Variable: None.
User Response: If you wish to keep a copy of the current Event Log for archiving purposes, move it to another directory. The Event Logger will automatically create a new file when it logs the next message. For information on managing the Event Log, see the "Reporting and Logging" chapter in the ACSLS Administrator's Guide.
Server system idle is pending.
Explanation: The ACSLM is in an idle-pending state and is therefore unavailable for requests using library resources.
Variable: None.
User Response: None.
CAP cap_id: Place cartridges in CAP.
Explanation: The specified CAP is ready to receive cartridges as a part of an enter operation. This message is repeated at approximately two-minute intervals until the CAP door is opened.
Variable: The cap_id is the identifier of the CAP.
User Response: Open the designated CAP door and place the cartridges in the CAP.
IPC failure on socket socket_id.
Explanation: The ACSLM or ACSSA cannot communicate with another library server software component.
Variable: The socket_id is the identifier of the failing socket.
User Response: If you did not issue an idle force command and the problem recurs, shut down and restart the library server software. Use the following procedure:
From a cmd_proc window, issue an idle request to place the library server in a quiescent state.
Log in as the acsss user, and shut down the library server using the kill.acsss utility.
Restart the library server using the rc.acsss utility.
If the problem continues, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
component component_id: Library error, error_type.
Explanation: An error in the library hardware has been reported to ACSLS.
Variable:
The component is the library component (for example, port or drive).
The component_id is the identifier of the library component.
The error_type is the type of error received from the library by the ACSLS server or encountered when ACSLS attempted to communicate with the library.
User Response: If the cause of the error is not obvious from this and other messages on the Event Log, report the error to Oracle Support. They should check the library and related hardware components to determine the cause of the library failure.
Server System network interface timeout.
Explanation: Due to lack of client response, a timeout has occurred during network data handling. Data such as earlier requests put in, or system responses may have been lost.
User Response:
Check the network connections on both the server system and the client system. If these are intact, the error may be due to network activity or momentary load.
If the error persists, verify network operations.
component component_id: Offline.
Explanation: The specified component was varied offline.
Variable:
The component is the library component (for example, ACS).
The component_id is the identifier of the library component.
User Response: None.
component component_Id: Online.
Explanation: The specified component was varied online.
Variable:
The component is the library component (for example, ACS).
The component_id is the identifier of the library component.
User Response: None.
Software process failure.
Explanation: A library request process failed. This may be due to either an error in request processing or an unexpected process termination. This error can be ignored if you just issued an idle force command.
Variable: None.
User Response: Retry the command and see if you get the same error. If you do, shut down and restart ACSLS:
From a Command Processor window, issue an idle request to place the library server in a quiescent state.
Log in as the acsss user, and shut down the library server using the kill.acsss utility.
Restart the library server using the rc.acsss utility.
It is recommended that you perform an audit to reconcile the database with the physical contents of the library.
Server system recovery complete.
Explanation: Library server recovery completed successfully.
Variable: None.
User Response: None.
Server system recovery failed.
Explanation: Library server recovery failed.
Variable: None.
User Response: Check previous Event Log entries for additional information about the failure. Follow the suggested action for the associated error message(s).
LSM lsm_id: In-transit cartridge recovery incomplete
Explanation: The specified LSM failed to recover all in-transit cartridges during library server recovery.
Variable: The lsm_id is the identifier of the LSM containing the in-transit cartridges.
User Response:
Query the LSM to make sure there are empty cells in the LSM.
If there are no empty cells in the LSM, eject cartridges to free cell space. See the "Cartridge Management" chapter in the ACSLS Administrator's Guide for information about ejecting cartridges.
Ensure that the CAP in the specified LSM is empty.
Vary the LSM offline, and then back online to attempt an in-transit cartridge recovery.
If this process is unsuccessful, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Server system recovery started.
Explanation: Library server recovery has been initiated.
Variable: None.
User Response: None.
CAP cap_id: Remove cartridges from CAP.
Explanation: The specified CAP contains cartridges, and is ready for the operator to remove them. This message is repeated at approximately two-minute intervals until the CAP door is opened.
Variable: The cap_id is the identifier of the CAP.
User Response: Open the designated CAP door and remove the cartridges.
Server system network interface failure.
Explanation: The CSI has encountered a Remote Procedure Call (RPC) failure. Data such as earlier requests you put in or system responses may have been lost.
Variable: None.
User Response: Check previous Event Log entries for additional information about the failure. Follow the suggested action for the associated error message(s).
Pool pool_id: high water mark warning.
Explanation: The number of volumes in the specified scratch pool is greater than or equal to the high water mark.
Variable: The pool_id is the pool identifier.
User Response: None. Unless cartridges are used from the pool or the high water mark threshold is reset, this message will be repeated when a volume is added to the specified scratch pool. See the "Cartridge Management" chapter in the ACSLS Administrator's Guide for information on managing scratch pools.
Pool pool_id: low water mark warning.
Explanation: The number of volumes in the specified scratch pool is less than or equal to the low water mark.
Variable: The pool_id is the pool identifier.
User Response: Follow your company's procedures for adding scratch volumes unless it is not a problem to run out of scratch volumes. See the "Cartridge Management" chapter in the ACSLS Administrator's Guide for information on managing scratch pools.
CAP cap_id: No CAP available, waiting.
Explanation: Audit processing has completed, but a CAP is not available for ejecting cartridges.
Variable: The cap_id indicates which ACS does not have a CAP available.
User Response: None. When a CAP is available, the cartridges will be ejected.
Drive drive_id: Cleaned.
Explanation: The specified drive has been cleaned.
Variable: The drive_id is the identifier of the library drive.
User Response: None.
CAP cap_id: CAP opened.
Explanation: The CAP has been opened.
Variable: The cap_id is the identifier of the CAP that was opened.
User Response: None.
CAP cap_id: CAP is uninstalled, inoperative or it is offline.
Explanation: The CAP is un-installed, inoperative, or is offline.
Variable: The cap_id is the identifier of the CAP whose door is open.
User Response: If the CAP is offline, make it online. If the CAP is un-installed or inoperative, use the other available CAP.
filesystem: Disk usage of current% pct exceeds limit of limit% pct.
Explanation: The available disk space in the indicated file system is about to run out of space. Appearance of this message is usually indicative of either the Event Log filling up disk space because it has not been periodically reset, or the database journal files are filling up disk space because a database backup has not been periodically done.
Variable:
The filesystem is the name of the disk subsystem that is about to run out of space.
The current is the current percentage of disk space used in the filesystem.
The limit is the disk threshold above which this message is periodically issued.
User Response:
See "ACSLS Event Log" in "Appendix B: Troubleshooting" in the ACSLS Administrator's Guide for information about managing the Event Log size and rollover files.
See the "Database Backup and Restore" chapter of the ACSLS Administrator's Guide for information about database backups and managing database redo log files.
Volume identifier vol_id deleted.
Explanation: The specified volume identifier has been removed from the ACSLS database. This typically occurs when volumes are ejected from the library. It may also occur when the specified volume is not found where it should be located (for example, because it was manually removed from the library).
Variable: The vol_id is the volume identifier of the volume that was deleted.
User Response: None. However, if you believe the volume was deleted in error, then report the error to Oracle Support. Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support").
CAP cap_id: Enter operation status.
Explanation: This message shows the status of an enter operation that is either in progress or completed.
Variable:
The cap_id is the identifier of the CAP.
The status is the current status of the enter operation and the CAP identified in the message.
User Response: None.
Server system terminated.
Explanation: This message indicates that the ACSLS server is being shutdown and will not take any more requests or commands.
Variable: None.
User Response: Wait for the completion of server shutdown and re-start the ACSLS server.
lib_cmpnt cmpnt_id configuration changed.
Explanation: The configuration of the library component identified by cmpnt_id, (such as LSM 0,0) changed.
Variable:
The lib_cmpnt is the library component type (LSM, ACS or CAP).
The cmpnt_id is the identifier of a library component, such as 0,0 (lsm_id).
User Response: None.
lib_cmpnt cmpnt_id port configuration changed.
Explanation: The port connections of an ACS identified by acs_id were changed.
Variable:
The lib_cmpnt is the library component, such as ACS.
The cmpnt_id identifies the ACS. This is an acs_id, such as 0.
User Response: None.
Unknown media type detected. Not Entered. Validate volumes placed in CAP.
Explanation: The media type of a volume found in the CAP is unknown to ACSLS, and the volume will not be entered into the library.
Variable: None.
User Response: Remove the cartridge from the CAP and check the media-type character on the label. Make sure that the label is readable and is associated with a valid tape device attached to the library. Multiple instances of this error may point to problems with the robotics vision system.
Backing up ACSLS control files.
Explanation: The backup of the ACSLS control files started.
Variable: None.
User Response: None.
Error backing up ACSLS control files control_file.
Explanation: There was an error while backing up the ACSLS control files control_file.
Variable: The control_file are the files in $ACS_HOME/data or $ACS_HOME/data/external.
User Response: Observe related error messages for clues to the possible cause of this condition.
ACSLS control files control_files successfully backed up to device.
Explanation: Backup of ACSLS control files to the backup device was successful.
Variable: The control_files are the files in $ACS_HOME/data or $ACS_HOME/data/external device in the tape device or file that the user is trying to backup to.
User Response: None.
Restoring ACSLS control files.
Explanation: The restore of the ACSLS control files started.
Variable: None.
User Response: None.
ACSLS control files control_files have been restored.
Explanation: Restore of the ACSLS control files completed successfully.
Variable: The control_files are the files in $ACS_HOME/data or $ACS_HOME/data/external.
User Response: None.
Cannot extract ACSLS control files from restore_file.
Explanation: There was an error while extracting ACSLS control files from the restore_file.
Variable: The restore_file is the file used for ACSLS restore.
User Response: Observe related error messages for clues to the possible cause of this condition.
Cannot rename source_file to destination_file.
Explanation: There was an error when moving source_file to destination_file
Variable:
The source_file is the file to be moved.
The destination_file is the target location.
User Response: Check if user performing the operation has necessary permissions.
Exiting Library configuration program because ACSSS services are currently running. To modify the library configuration, first 'idle' the library server and then run the command,'acsss disable'.
Explanation: The acsss_config routine discovered that ACSLS is running.
Variable: None.
User Response: You must bring down ACSSS services before you can run acsss_config. To do this, run acsss disable.
ACSLS control files export failed. Database export was successful though.
Explanation: There was an error during the export of ACSLS control files. However, the export of ACSLS database completed successfully.
Variable: None.
User Response: Observe related Event Log messages for clues as to the possible cause of this condition.
An export file of the ACSLS control files matching the exported database table data in import_file is not found. If ACSLS has been newly installed (or re-installed), this import will not be able to restore any previous product customization, such as access control or scratch preferences.
Explanation: ACSLS control files will not be a part of import_file if export was done from the pre-ACSLS 5.2 release.
User Response: None.
ACSLS control files import failed. Database import was successful though.
Explanation: There was an error during the import of ACSLS control files. However, the import of ACSLS database completed successfully.
Variable: None.
User Response: Observe related Event Log messages for clues as to the possible cause of this condition.
Please place the ACSLS export cartridge in the tape drive.
Explanation: An operation which uses a tape device was started.
Variable: None.
User Response: Place the correct tape containing the exported ACSLS database files in the tape drive.
Check Tape Device tape_device: Problems with the ACSLS export tape.
Explanation: An operation that uses the tape device was started.
Variable: The tape_device is the Tape device used for exporting ACSLS data.
User Response: Correct the problems seen with the tape drive.
Beginning database export phase.
Explanation: The export of the ACSLS database was started.
Variable: None.
User Response: None.
ACSLS must not be running to facilitate database imports and exports. Execute the ACSLS server shutdown script (kill.acsss).
Explanation: This error is logged when you try to stop the database while ACSLS is running. This is not allowed since the application communicates extensively with the database. The ACSLS application must be shut down prior to shutting down the database.
Variable: None.
User Response: Stop ACSLS by executing the commands idle and kill.acsss. Shut down the database server using db_command stop.
Beginning database import phase.
Explanation: The export of the ACSLS database was started.
Variable: None.
User Response: None.
ACSSS services must not be running while managing database imports and exports. Bring down non-database services with acsss disable.
Explanation: The import or export utility discovered that ACSSS services are running.
Variable: None.
User Response: You must first bring down the ACSSS services in order to import or export the ACSLS database. To do this, use acsss disable.
Extracting ACSLS control files.
Explanation: The extraction of the ACSLS control files was started.
Variable: None.
User Response: None.
Unable to start ACSLS database.
Explanation: There was an error while starting ACSLS Database.
Variable: None.
User Response: See ACSLS Database log files. If you need assistance, gather the information required, described above, and collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
ACSLS database recovery started.
Explanation: This message is logged when the ACSLS database recovery is started.
Variable: None.
User Response: None.
ACSLS recovery successfully completed.
Explanation: Restore of ACSLS completed successfully.
Variable: None.
User Response: None.
ACSLS database recovery successfully completed. Database has been restored to the point of the last backup plus any subsequent transactions recorded on the current disk.
Explanation: This message indicates that the recovery you ran has completed. The second part of the message can mean that all transactions were recovered unless you have the following conditions:
You do not have a second disk, just a primary disk.
Your primary disk was damaged and you ran a recovery.
Under these conditions, it is possible that not all transaction files were recovered after running the recovery. Chances are likely that redo logs were not applied since they were corrupted by the same problem that prompted the restore.
If you do have a second disk or you have only a primary disk that did not crash, it is likely that all transactions were restored.
Variable: None.
User Response: None.
The backup media (in device) does not appear to have been generated by ACSLS database export. Please check and retry the operation with a valid tape or file.
Explanation: The ACSLS database import has failed because of a wrong input file or tape_device is specified.
Variable: The device is the tape device or file from which the user is trying to import.
User Response: Use correct file or tape_device.
Failed to add necessary CRON entry for PostGres log management.
Explanation: There was an error while adding cron entries for PostgreSQL log management.
Variable: None.
User Response: Verify if user has necessary permissions to add cron entry.
Unable to kill yapilh or yapiDP/sl4000DP PID(s) pids.
Explanation: A library handler or device process was still running when the product came up. These processes must be killed before the product can restart.
Variable: The pids are the related process IDs that still appear to be running.
User Response:
As acsss, kill the related processes by running the stopYAPILH.sh script.
If stopYAPILH.sh does not work when run as acsss, run it as root.
If restarting ACSLS fails after three tries, collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Unable to kill scsilh or scsiDP PID(s) pids.
Explanation: A scsilh library handler or device process was still running when the product came up. These processes must be killed before the product can restart.
Variable: The pids are the related process IDs that still appear to be running.
User Response:
As acsss, kill the related processes by running the stopSCSILH.sh script.
If stopSCSILH.sh does not work when run as acsss, run it as root.
If restarting ACSLS fails after three tries, collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
ACS acs_id, lib_handler PID pid, driver_state state.
Explanation: A library handler process is reporting its state when being terminated. This might occur during some error recovery activity, for example, or during cleanup of stale processes at startup.
Variable:
The acs_id is the ACS which is reporting the problem.
The lib_handler is the library handler that was found (scsilh or yapilh).
The pid is the process ID for the handler that is still running.
The state is the run state of the handler being killed.
User Response: This may only be the reporting of process cleanup. Verify that ACSLS is running as expected. If not, you may need to run the stop script for the reported library handler before re-starting ACSLS.
As acsss, kill the library handler process by running the appropriate stop script.
This will be either stopSCSILH.sh or stopYAPILH.sh, based on library handler.
If the script does not work when run as acsss, run it as root.
If the script also fails when run as root, collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Killing lib_handler process pid with signal failed on error_desc, errno= error_no
Explanation: A library handler process was still running when the product came up or was shut down. This process must be killed before the product can restart.
Variable:
The lib_handler is the library handler that was found running.
The pid is the process ID of the library handler.
The signal is the system signal that was issued when killing the process.
The error_desc is the UNIX error description associated with error_no.
The error_no is the Unix error number returned by the kill() system call.
User Response:
As acsss, kill the library handler process by running the appropriate stop script.
This will be either stopSCSILH.sh or stopYAPILH.sh, based on library handler.
If the script does not work when run as acsss, run it as root.
If the script also fails when run as root, collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Invalid driver_state state for Connect/Vary request ACS ACS_id port_name.
Explanation: This error message indicates an ACSLS software error.
Variable:
The state is the state of the driver, in the form STATE_<NAME_OF_STATE>.
The acs_id is the identifier of the ACS receiving the request.
The port_name is the name of the port in the Connect/Vary request.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Cleanup of lib_handler failed, rerun stop_script manually, errno error_desc
Explanation: A library handler process was still running when the product came up or was shut down. This process must be killed before the product can restart.
Variable:
The lib_handler is the process that failed to terminate (scsilh or yapilh).
The stop_script is the ACSLS shell script used to terminate this process.
The error_desc is the UNIX error description returned by the system() call.
User Response:
As acsss, kill the library handler process by running the appropriate stop script.
This will be either stopSCSILH.sh or stopYAPILH.sh, based on library handler.
If the script does not work when run as acsss, run it as root.
If the script also fails when run as root, collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Cleanup of lib_handler failed, rerun stop_script manually, return code return_code.
Explanation: A library handler process was still running when the product came up or was shut down. This process must be killed before the product can restart.
Variable: The return_code is the return code from the ACSLS shell script stopSCSILH.sh.
The lib_handler is the process for which the operation failed.
The stop_script is the ACSLS shell script used to terminate this process.
The return_code is the return code from the ACSLS shell script.
User Response:
As acsss, kill the library handler process by running the appropriate stop script.
This will be either stopSCSILH.sh or stopYAPILH.sh, based on library handler.
If the script does not work when run as acsss, run it as root.
If the script also fails when run as root, collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
ACS acs_id: fork of lib_handler failed errno(error_no) error_desc
Explanation: The UNIX system call fork had an error when attempting to start a library handler process.
Variable:
The acs_id is the ACS which is reporting the problem.
The lib_handler is the process for which the operation failed.
The error_no is the UNIX error number returned by the fork() system call.
The error_desc is the UNIX error description associated with error_no.
User Response: Restart ACSLS and if the problem persists, collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
execl (program) failed, errno=error_desc
Explanation: The UNIX system call execl failed executing program.
Variable:
The program is the program that execl tried to execute.
The error_desc is the UNIX error description associated with errno returned by the UNIX execl system call.
User Response: Restart ACSLS and if the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
lib_handler did not start, acslh exiting
Explanation: This message refers to a fatal error in either ACSLS, SCSILH, or the UNIX system. The product will shut down as part of this message.
Variable: The lib_handler is the process that failed to start (scsilh or yapilh).
User Response: Restart ACSLS and if the problem persists, collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
return code (return_code) terminated scsilh.im.
Explanation: SCSILH terminated without a signal. If this message occurred during shutdown of ACSLS, it is informational only. Otherwise, see Action Required below.
Variable: The return_code is the code returned by SCSILH.
User Response: Restart ACSLS. If ACSLS does not restart after three tries, contact collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support. Please have return code available.
Drive drive_id: Unable to position on the drive, status: loaded.
Explanation: The drive is loaded. The robot was unable to target on the drive.
Variable: The drive_id is the drive identifier.
User Response: Drive is reporting a problem. This could be due to the drive or to the robot. Do the following:
Check the drive for a stuck tape.
If there are no problems in the drive, check the LMU and LSM error logs for more information.
Unable to create filename file.
Explanation: An ACSLS utility could not create a required file.
Variable: The filename is the name of the file to be created.
User Response: Make sure that the /tmp directory has write permission for all users, then rerun the backup.
Unable to read files from backup device, dev.
Explanation: The rdb.acsss utility cannot read the backup files from the specified backup device.
Variable: The dev is the backup device you specified.
User Response: Rerun the restore operation, specifying a valid device with a valid backup file created by the bdb.acsss utility.
The backup device dev is not a good bdb backup from ACSLS release. Please try again specifying a valid bdb backup
Explanation: The rdb.acsss utility cannot verify that the specified backup files are valid.
Variable:
The dev is the backup device you specified.
The release is the ACSLS release you are running.
User Response: You must restore the database from a backup created by the bdb.acsss utility from the same version of ACSLS (release) that you are running. Rerun the restore operation, specifying a valid device with a valid backup file created by the release version of the bdb.acsss utility.
Too many processes. With the current settings specified through acsss_config, ACSLS requires no_req_pro processes to be running simultaneously. Currently, your system limit allows only sys_limit_no_pro_user processes per user. Either lower the number of mount processes, persistent query processes or transient processes, or else raise this system limit.
Explanation: Message is self-explanatory.
Variable:
The no_req_pro is the number of required processes.
The sys_limit_no_pro_user is the system limit on the number of processes per user.
User Response: Do one or more of the following:
Lower the number of persistent query processes through acsss_config.
Lower the number of mount processes through acsss_config.
Lower the maximum number of transient processes through acsss_config.
Raise the maximum allowable number of processes per user. (This is system-dependent.).
<this_mem> is insufficient memory. <recommended_mem> is recommended.
Explanation: A check for sufficient memory space is made during the installation of ACSLS. If the server lacks sufficient memory, this message displays with the actual (installed) value and the recommended value of physical memory.
Variable:
The this_mem is the actual physical memory installed.
The recommended_mem is the amount of memory recommended for this version of ACSLS.
User Response: To avoid sluggish behavior and other operational difficulties with ACSLS, you should equip the machine with the recommended minimum amount of physical memory.
<current_swap> is insufficient swap. <min_swap> is recommended.
Explanation: A check for sufficient swap space is made during the installation of ACSLS. If the server lacks sufficient swap, this message displays with the currently configured value and the recommended value of swap space.
Variable:
The current_swap is the amount of swap space currently configured.
The min_swap is the amount of swap space recommended for this version of ACSLS.
User Response: To avoid sluggish behavior and numerous operational difficulties with ACSLS, you should configure the system with the recommended amount of swap space.
RPtimeout value for keyword is not numeric.
Explanation: In the $ACS_HOME/data/internal/RPtimeout file the value for keyword was not all numeric data. This message will be followed by message 1974.
Variable: The keyword represents the operation that has the corresponding timeout value.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
RPtimeout value for keyword is not in range.
Explanation: In the $ACS_HOME/data/internal/RPtimeout file the value for keyword was not in the range of 1 second to 24 hours. This message will be followed by message 1974. The default value for keyword will be used.
Variable: The keyword represents the operation that has the corresponding timeout value.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Unable to find keyword in RPtimeout file.
Explanation: In the file, ACSLS was unable to find the keyword. This message is followed by message 1974, which will give the keyword.
Variable: The keyword represents the operation that has the corresponding timeout value.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Unable to open RPtimeout file.
Explanation: ACSLS attempted to open $ACS_HOME/data/internal/RPtimeout, but was unable to do so. The default value will be used. This message is followed by message 1974, giving the keyword.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Using default timeout value for keyword.
Explanation: This message follows message 1970, 1971, 1972, or 1973 to inform you that the default timeout value was used for the LH request type keyword.
Variable: The keyword represents the operation that has the corresponding timeout value.
User Response: None. Action applies to the message that preceded this one.
Failed to get queue member.
Explanation: Message was not retrieved from the message queue for removal.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Do not have read permission.
Explanation: The CSI does not have read permission on the csi_ip_switch.dat file.
Variable: None.
User Response: Use chmod to set permissions on the csc_ip_switch.dat file for read and write access for the user.
Cannot open file errno=error_no.
Explanation: A failure of type errno occurred when the csi_ip_switch.dat file was attempted to be opened.
Variable: The error_no is the system error number associated with opening this file.
User Response: Check that the file csc_ip_switch.dat exists and is in the proper location: $ACSLS_HOME/data/internal/client_config/. If both of these conditions are met and the problem continues, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support. For more information about managing a dual-LAN client configuration, see ”Managing a Dual-Lan Client Configuration” in the ”Library Management” chapter of the ACSLS Administrator's Guide.
Invalid entry displayed_line - line ignored.
Explanation: The line displayed is an invalid entry and the line is ignored.
Variable: The displayed_line is the invalid line that needs to be corrected.
User Response: Correct the line displayed and restart ACSLS.
Duplicate addresses displayed_line - line ignored.
Explanation: Duplicate primary and secondary addresses that were entered into the csc_ip_switch.dat file.
Variable: The displayed_line is the invalid line that needs to be corrected.
User Response: Correct the line displayed and restart ACSLS.
Max number of (max_no_allowed) dual clients exceeded.
Explanation: More than the maximum number of allowable dual clients were entered into the csc_ip_switch.dat file. Only the maximum number of dual clients is allowed.
Variable: The max_no_allowed is the maximum number of allowable dual clients entered into the csc_ip_switch.dat file.
User Response: Do not exceed the maximum number of allowable dual clients in the csc_ip_switch.dat file. If you need more clients, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Bad primary addr - bad conversion: displayed_addr.
Explanation: The primary address entered into the csc_ip_switch.dat file is not an IP address format.
Variable: The displayed_addr is the erroneous primary address displayed.
User Response: Correct the displayed address in the csc_ip_switch.dat file and restart ACSLS.
Bad primary addr - not digital: displayed_addr.
Explanation: The primary address entered in the csc_ip_switch.dat file is not an IP address format.
Variable: The displayed_addr is the erroneous primary address displayed.
User Response: Correct the displayed address in the csc_ip_switch.dat file and restart ACSLS.
Bad secondary addr - bad conversion: displayed_addr.
Explanation: The secondary address entered in the csc_ip_switch.dat file is not an IP address format.
Variable: The displayed_addr is the erroneous secondary address displayed.
User Response: Correct the displayed address in the csc_ip_switch.dat file and restart ACSLS.
Bad secondary addr - not digital: displayed_addr.
Explanation: The secondary address entered in the csc_ip_switch.dat file is not an IP address format. The address is not digital.
Variable: The displayed_addr is the erroneous secondary address displayed.
User Response: Correct the displayed address in the csc_ip_switch.dat file and restart ACSLS.
path opened - DUAL PATH OPTION ACTIVATED.
Explanation: File (csc_ip_switch.dat) was opened and read successfully. Dual path function is activated.
Variable: The path is the full path to the csc_ip_switch.dat file.
User Response: None.
path opened - Dual Option Process Failure.
Explanation: A major process failure has occurred when trying to de-queue primary address packets.
Variable: The path is the full path to the csc_ip_switch.dat file.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
LMU error: ACS: acs_id Invalid value found in transmission, value = character.
Explanation: The ACSLS (library handler process) detected an invalid character in the transmission received from the LMU.
Variable:
The acs_id is the ACS identifier.
The character is the invalid character detected in the transmission.
User Response: If the request failed, reissue the request.
LMU error: ACS: acs_id Invalid lmu_mode lmu_mode.
Explanation: The ACSLS (library handler process) received a response packet from the LMU with an unrecognizable LMU code specified in lmu_mode.
Variable:
The acs_id is the ACS identifier.
The lmu_mode is the LMU mode from which the response was received. This mode is one of the following: active, standby, or standalone.
User Response: None.
LMU error: ACS: acs_id Invalid compatibility level compat_level line = line_number.
Explanation: An invalid LMU compatibility level was detected.
Variable:
The acs_id is the ACS identifier.
The compat_level is the invalid compatibility level detected.
The line_number is the location in the ACSLS code where the error was detected.
User Response: None.
ACS: acs_id Library Recovery Complete.
Explanation: The ACSLH (library handler process) has completed the processing of library requests that were affected by a switch LMU, library IPL, or when communication with the library was lost and has been re-established.
Variable: The acs_id identifies the ACS.
User Response: None. This message is informational only.
ACS: acs_id New Active LMU.
Explanation: The ACSLS (library handler process) has received an unsolicited message from the LMU indicating that there is a new Active LMU.
Variable: The acs_id is the ACS identifier.
User Response: None.
LMU error: ACS: acs_id Invalid lmu_name lmu_name.
Explanation: The ACSLS (library handler process) received a packet from the LMU with an unrecognizable LMU name specified in the lmu_name portion of the packet.
Variable:
The acs_id is the ACS identifier.
The lmu_name is the name of the LMU from which the packet was received: A, B, or standalone.
User Response: None.
LMU error: ACS: acs_id Invalid standby_status standby_status.
Explanation: An unexpected status for a standby LMU has been returned in the response to a query lmu request.
Variable:
The acs_id is the ACS identifier.
The standby_status is the unexpected value which was received.
User Response: Check the status of the port used by ACSLS to communicate with the standby LMU for the specified ACS. A vary port command may correct the status of the LMU. If the error persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
ACS: acs_id Standby LMU now communicating.
Explanation: The standby LMU is communicating to the specified ACS.
Variable: The acs_id is the ACS identifier.
User Response: None.
ACS: acs_id Standby LMU not communicating.
Explanation: The ACSLH (library handler process) has received an unsolicited message from the LMU indicating that the Standby LMU is not communicating with the ACSLS server.
Variable: The acs_id is the ACS identifier.
User Response: None.
ACSLH: Request Recoverer: message.
Explanation: This message usually displays when a software error occurs during a dual LMU switchover recovery or in the recovery period after a standalone LMU IPLs.
Variable: The message gives a detailed description of the error.
User Response: Have the error description from message available, and collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
status = port_status: Cannot vary last Active port offline, leaving port online.
Explanation: Issuing a vary port offline command to the last online active port is not allowed.
Variable: The port_status is the status of the port.
User Response: None.
Standalone LMU, cannot initiate switch.
Explanation: Issuing a switch LMU command to a standalone LMU is not allowed.
Variable: None.
User Response: None.
Standby LMU not communicating, cannot initiate switch.
Explanation: Issuing a switch LMU command when the standby LMU is not communicating is not allowed.
Variable: None.
User Response: None.
ACS acs_id has no LSMs configured; you may want to verify hardware configuration.
Explanation: This message may appear in either of the following conditions:
If the ACS was configured with ports that are actually connected to different ACSs
If you have a dual-LMU configuration and a switchover occurs during acsss_config, it is possible to get this message when one of the LMUs IPLs during acsss_config.
Variable: The acs_id is the ACS that has no LSMs configured.
User Response:
If you see this message during product configuration, verify all hardware configuration and all hardware connections. These connections include those to the server, from the LMUs to the LSMs, and between the LMUs in a dual-LMU configuration.
If all hardware connections are correct and acsss_config still detects an empty ACS, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
If this message occurs with an LMU switchover during acsss_config, rerun acsss_config.
Could not find text text in file filename.
Explanation: Some expected text in the specified file was not found. The file could possibly be corrupted.
Variable:
The text is the text that was expected to be in that file.
The filename is the file.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error processing command: command - error.
Explanation: This message occurs when there is an error processing a command received within ACSLS.
Variable:
The command is the command that caused the error.
The error is the specific error that occurred.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Ipc error reading command: error.
Explanation: There was an internal communication error when trying to read a command for processing.
Variable: The error encountered during IPC.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Unable to get value for TRACE_VOLUME dynamic variable.
Explanation: There was an error retrieving the value for the TRACE_VOLUME dynamic variable. This will result in possible inconsistent behavior with respect to volume tracing.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error trying to create volume statistics entry.error_desc.
Explanation: There was a problem when trying to create an entry in the LIB_VOL_STSTS file.
Variable: The error_desc is the detailed error message describing the problem.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Move to cell_id failed cartridge recovery needed. Volume vol_id may be stuck intransit.
Explanation: Volume is stranded inside the LSM somewhere between its original source and destination.
Variable:
The cell_id is the destination cell address.
The vol_id is the volume identifier of stuck volume.
User Response: Do either of the following:
Manually remove the tape from LSM, then audit its cell and enter it.
Perform a vary offline force the LSM the volume is in; then vary the LSM online to force in-transit recovery.
Error updating cell cell_id state to full.
Explanation: There was an error in setting a cells' state to full. This may have resulted in an inconsistent ACSLS database.
Variable: The cell_id is the cell address that had the error.
User Response: Perform a subpanel audit of the cell indicated to attempt to reconcile the database.
Error updating cell cell_id state to empty.
Explanation: There was an error in setting a cells' state to empty. This may have resulted in an inconsistent ACSLS database.
Variable: The cell_id is the cell address that had the error.
User Response: Perform a subpanel audit of cell the indicated to attempt to reconcile the database.
Error updating cell cell_id state to reserved.
Explanation: There was an error in setting a cells' state to reserved. This may have resulted in an inconsistent ACSLS database.
Variable: The cell_id is the cell address that had the error.
User Response: Perform a subpanel audit of the cell indicated to attempt to reconcile the database.
Idle command failed information.
Explanation: An attempt to idle a portion of the ACSLS server failed.
Variable: The information is the detailed information about the failure.
User Response: The server will still be functional but you should report the problem as it may be a symptom of a larger problem. Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Failed to close accept socket. Error: error.
Explanation: There was an error when attempting to close an internal ACSLS communication mechanism.
Variable: The error is the specific error that caused the failure.
User Response: This error could indicate a one-time anomaly, or it could be a symptom of a bigger, underlying problem. If this message appears one time with no other error messages, then it can be ignored. If it appears multiple times or with other error messages, then collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Database Error: error.
Explanation: There was an error processing a transaction with the database used by ACSLS.
Variable: The error is the specific error that occurred with the database.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Invalid data found in command: information.
Explanation: ACSLS detected some invalid data in an internal command structure.
Variable: The information is a detailed description of invalid data.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Unexpected ACSLH result received by move: information.
Explanation: An internal error occurred in the communication between ACSLS components.
Variable: The information is detailed information about the error.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Internal error in processing the move command: information.
Explanation: An internal error occurred while processing a move request.
Variable: The information is detailed information about the error.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error getting LIB_VOL_STATS value: explanation.
Explanation: ACSLS was unable to read the value for the LIB_VOL_STATS dynamic variable. This may result in a failure to log volume statistic entries.
Variable: The explanation is detailed information about the error.
User Response: Rerun acsss_config to attempt to turn on LIB_VOL_STATS and then attempt the request again. If the error persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error creating record for Volume vol_id: information.
Explanation: An internal error occurred while attempting to update the ACSLS internal database record for the given vol_id..
Variable:
The vol_id is the volume identifier of the volume that failed to create.
The information is detailed information about the error.
User Response: Attempt to audit the expected location of the volume. If that fails, then collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Unable to update status for Volume vol_id: information.
Explanation: An internal error occurred while attempting to update the ACSLS internal database record for the given vol_id.
Variable:
The vol_id is the volume identifier of the volume that failed to create.
The information is detailed information about the error.
User Response: Attempt to audit the expected location of the volume. If that fails, then collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
move: volume (vol_id) not found in cell (cell_id), deleted.
Explanation: When attempting to move a volume, the volume was not found in its home cell. The volume record is deleted from the database.
Variable:
The vol_id is the volume identifier of the volume that was not found.
The cell_id is the cell location.
User Response: Audit the LSM to reconcile the ACSLS database with the contents of the LSM.
cl_vol_write failed: vol_id.
Explanation: The process failed to update the volume record in the database.
Variable: The vol_id is the volume ID for the volume record that failed to be updated in the database.
User Response: Display the volume. Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Attempting to log an invalid message (message_number) from a client thread.
Explanation: A CSI client thread returned an unsupported message number to the main CSI thread. The message is ignored.
Variable: The message_number is the unsupported message number.
User Response: None. CSI processing continues without problems. If desired, report this message to Oracle Support.
XDR translation failed.
Explanation: The XDR translation of a response failed. An earlier message probably pinpoints the exact problem. The CSI is not able to send this response to the network client.
Variable: None.
User Response: Collect relevant logs, especially the acsss_event.log, and report this problem to Oracle Support
Sending first response to client ip_address.
Explanation: This message is reported when the first response is sent to a network client.
Variable: The ip_address is the IP address of the network client.
User Response: None.
Unable to allocate shared queue for client ip_address.
Explanation: The CSI was unable to allocate a shared queue for responses to the specified network client. No responses will be returned to this client until this problem is corrected.
Variable: The ip_address is the IP address of the network client.
User Response: Determine if the ACSLS server is out of memory. Use vmstat or vmstat –s and look for pages swapped out. If the ACSLS server is not out of memory, collect diagnostic information and contact Oracle Support.
Unable to add entry to shared queue for client ip_address.
Explanation: The CSI was unable to add a response to the shared queue for the specified network client. This response will be dropped.
Variable: The ip_address is the IP address of the network client.
User Response: Determine if the ACSLS server is out of memory. Use vmstat or vmstat –s and look for pages swapped out. If the ACSLS server is not out of memory, collect diagnostic information and contact Oracle Support.
Unable to create thread for client ip_address.
Explanation: The CSI was unable to create a thread to send responses to the specified network client. No responses will be returned to this client until the problem is corrected.
Variable: The ip_address is the IP address of the network client.
User Response: Determine if the ACSLS server is out of memory. Use vmstat or vmstat –s and look for pages swapped out. If the ACSLS server is not out of memory, collect diagnostic information and contact Oracle Support.
Unable to create clients queue.
Explanation: The CSI was unable to create the list of all network clients, and is unable to return responses to clients until it can create this list.
Variable: None.
User Response: Determine if the ACSLS server is out of memory. Use vmstat or vmstat –s and look for pages swapped out. If the ACSLS server is not out of memory, collect diagnostic information and contact Oracle Support.
Unable to create response queue.
Explanation: The CSI was unable to create the queue for responses from client threads to the main CSI thread. The CSI may have problems returning responses to clients until it can create the response queue.
Variable: None.
User Response: Determine if the ACSLS server is out of memory. Use vmstat or vmstat –s and look for pages swapped out. If the ACSLS server is not out of memory, collect diagnostic information and contact Oracle Support.
Discarding packet for client ip_address with SSI identifier of request_id.
Explanation: A response to a request from a network client was discarded. The response was either an Acknowledgement to a request from a client or a response to a request. It may not have been sent because of network problems or because ACSLS is shutting down. If ACSLS is not shutting down, the CSI continues to attempt to return other responses.
Variable:
The ip_address is the IP address of the network client.
The request_id uniquely identifies this request that is assigned by the SSI (on the network client).
User Response: See associated messages for more details. If ACSLS is not shutting down, determine if there may be network problems between the client and the ACSLS server.
Pthread function failed with return code return_code.
Explanation: The indicated thread function failed with the given return code. The ACSLS CSI is not operating properly.
Variable: The return_code uniquely identifies the request assigned.
User Response: Collect relevant logs, especially the acsss_event.log, and report this problem to Oracle Support.
Resetting bad RPC file descriptor rpc_fd.
Explanation: This message logs recovery from an RPC error. CSI automatically resets the RPC file descriptor, and processing continues.
Variable: The rpc_fd is the RPC file descriptor that was reset.
User Response: None. The CSI automatically resets the RPC file descriptor, and processing continues.
Unable to shift transaction log file on secondary disk.
Explanation: The secondary disk manager is unable to create the transaction log file on the secondary disk. This is a database error.
User Response: Rerun the secondary disk manager (sd_mgr.sh).
Cannot allocate environment handle.
Explanation: The ODBC call to allocate the environment handle has failed.
Variable: None.
User Response: The application has to be re-started. Contact your System Administrator.
Cannot allocate database handle.
Explanation: The ODBC call to allocate the database handle has failed.
Variable: None.
User Response: The application has to be re-started. Contact your System Administrator.
Cannot allocate statement handle.
Explanation: The ODBC call to allocate the SQL statement handle has failed.
Variable: None.
User Response: The application has to be re-started. Contact your System Administrator.
Cannot free connection handle.
Explanation: The ODBC call to free database connection handle has failed.
Variable: None.
User Response: None.
Cannot free environment handle
Explanation: The ODBC call to free the environment handle has failed.
Variable: None.
User Response: None.
Cannot fetch. Return code return_code
Explanation: The ODBC call to fetch a row from the query result set has failed.
Variable: The return_code is the error code number returned by ODBC.
User Response: The application has to be re-run. Contact your System Administrator.
Error in preparing statement.
Explanation: The ODBC call to prepare an SQL statement for execution has failed.
Variable: None.
User Response: The application has to be re-run. Contact your System Administrator.
Cannot reset auto commit option.
Explanation: The ODBC call to set orreset the automatic commit option for all database transactions has failed.
Variable: None.
User Response: The application has to be re-run. Contact your System Administrator.
Attempt to database recovery was aborted by the user.
Explanation: During database recovery, a warning message is prompted to the user for overwriting the current database. Database recovery cannot be interrupted once it starts. With this message, the user has selected to discontinue with the database recovery process.
Variable: None.
User Response: None.
Could not create the filename file.
Explanation: The file creation command failed. This message is logged when the installation program is unable to create the odbc.ini file. The installation program fails to create this file when any one of the following environment variables is not set: $ACS_HOME; $INFORMIXDIR; or $HW_PLATFORM
Variable: The filename is the odbc.ini file.
User Response: Check whether the above-mentioned variables are set. If these are not set, please reinstall ACSLS.
ACSLS database gentle shutdown did not succeed.
Explanation: Gentle shutdown of the database failed. This error is logged when the command fails after 10 retries.
Variable: None.
User Response:
If the error occurred during initial installation, reinstall the product and retry.
If the existing database is corrupted, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
ACSLS database forced shutdown did not succeed.
Explanation: The forced shutdown failed.
User Response:
If the error occurred during initial installation, reinstall the product and retry.
If the existing database is corrupted, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
ACSLS database fast shutdown did not succeed.
Explanation: The fast shutdown failed.
User Response:
If the error occurred during the initial installation, reinstall the product and retry.
If the existing database is corrupted, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
There remains only % MB of free space for ACSLS database space.
Explanation: Insufficient space for the ACSLS database.
Variable: The % is the percentage of free space.
User Response: Contact Oracle Support.
ACS: acs_id Standby LMU now communicating with active.
Explanation: The standby LMU for the specified ACS has resumed communicating with the active LMU for that ACS over their internal connection. You will see that the communication status between ACSLS and the standby LMU is tracked separately, and can be displayed using the query lmu command.
Variable: The acs_id is the ACS identifier.
User Response: None. This message is informational only, and replaces message number 2031.
ACS: acs_id Standby LMU not communicating with active.
Explanation: The standby LMU for the specified ACS has stopped communicating with the active LMU for that ACS over their internal connection. The communication status between ACSLS and the standby LMU is tracked separately, and can be displayed using the query lmu command.
Variable: The acs_id is the ACS identifier.
User Response: No action is required for ACSLS, which continues communicating with the active LMU. This message is informational only, and replaces message number 2032. This message would typically be seen when an IPL of the standby LMU is performed. Once the IPL is complete, message 2131 would be expected, indicating that internal communication between the LMUs has resumed. If this does not occur, it may indicate a problem. Check the LMUs, verifying that both are operational and that the LAN cable(s) between them are properly connected.
LMU error: ACS: acs_id Invalid active_status active_status.
Explanation: An unexpected status for an active LMU has been returned in the response to a query lmu request.
Variable:
The acs_id is the ACS identifier.
The active_status is the unexpected value which was received.
User Response:
Check the status of the port used by ACSLS to communicate with the active LMU for the specified ACS. A vary port command may correct the status of the LMU.
If the error persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Module: Selecting another volume because scratch or cleaning volume vol_id may be in use.
Explanation: ACSLS selected a cartridge for a mount scratch or an automated cleaning request and was updating the database. However, the cartridges' home cell was already reserved. ACSLS may call Cartridge Recovery to investigate the cell and volume, and may try to select a different scratch or cleaning cartridge.
Variable:
Module is the ACSLS module displaying this message.
The vol_id is the ACS identifier.
User Response: None.
Cannot cancel automatic enter at CAP cap_id
Explanation: A cancel was attempted on an automatic enter request, which is not allowed.
Variable: The cap_id identifier of the CAP where the automatic enter could not be cancelled.
User Response: None.
Cannot cancel this request type: request_type
Explanation: A cancel was attempted on a request type, request_type, that was not allowed.
Variable: The request_type is the request type not allowed.
User Response: None.
CAP proc_id: CAP cap_id is in a partitioned library, but the CAP is not dedicated to this partition. Therefore, it cannot be set to automatic mode
Explanation: An attempt was made to set CAP cap_id to automatic mode, but automatic mode is disallowed in a partitioned library unless the CAP is dedicated to this partition.
Variable:
The proc_id is the name of the procedure issuing the error message.
The cap_id identifies the CAP.
User Response: None.
CAP cap_id is already reserved in partition partition_num by host host_id.
Explanation: An attempt was made to use a CAP cap_id, but failed due to a prior CAP reservation by another partition.
Variable:
The cap_id is the CAP you attempted to use.
The partition_num is the partition which current holds the CAP reservation.
The host_id is the identifier of the host using the partition that has the CAP reserved.
User Response: In order for the CAP operation to complete, the CAP must be made available. This should be done by ending the processing of the host which is using the CAP. If that cannot be done, see the library procedures for overriding a CAP reservation.
CAP cap_id received an unexpected CAP door opened message; ignoring.
Explanation: The ACSLM received an unexpected message pertaining to a CAP door opening event.
Variable: The cap_id is the CAP you attempted to use.
User Response: None.
CAP cap_id received an unexpected CAP door closed message; ignoring.
Explanation: The ACSLM received an unexpected message pertaining to a CAP door closing event.
Variable: The cap_id is the CAP you attempted to use.
User Response: None.
CAP cap_id has been set to manual mode because the CAP is now shared; it is no longer dedicated to this partition.
Explanation: The CAP is no longer dedicated to this partition and therefore cannot be in automatic mode; a CAP must be in manual mode when it is being shared.
Variable: The cap_id identifies the CAP.
User Response: None.
CAP cap_id is in a partitioned library, and the CAP is dedicated to another partition. Please run Dynamic Config or acsss_config to remove the CAP from the configuration for this ACS. The CAP will be varied offline.
Explanation: The CAP is no longer accessible to this partition, and therefore, should be removed from the configuration.
Variable: The cap_id identifies the CAP.
User Response: Either run the Dynamic Configuration utility to update the configuration for the ACS (config acs acs_id), or shutdown ACSLS and run acsss_config to reconfigure the ACS.
The library reports CAP cap_id as not installed. Please run Dynamic Config or acsss_config to remove the CAP from the configuration. The CAP will be varied offline.
Explanation: The CAP is no longer installed in the library, and therefore, should be removed from the configuration.
Variable: The cap_id identifies the CAP.
User Response: Either run the Dynamic Configuration utility to update the configuration for the ACS (config acs acs_id), or shutdown ACSLS and run acsss_config to reconfigure the ACS.
Intermediate dismount response not received when dismounting volume vol_id from drive drive_id.
Explanation: ACSLS did not receive the informational only response from the library on a dismount.
Variable:
The vol_id identifies the volume.
The drive_id identifies the drive.
User Response: None.
proc_id: Maintenance required for component component_id.
Explanation: The library reported a problem with the specified component.
Variable:
The proc_id is the name of the procedure issuing the error message.
The component identifies the component type (volume or drive).
The component_id identifies the component.
User Response: Contact Oracle Support to have the component inspected.
Fault Symptom Code (FSC) fsc reported when dismounting volume vol_id from drive drive_id.
Explanation: The drive reported a Fault Symptom Code (FSC) on a dismount.
Variable:
The fsc is the four-digit Fault Symptom Code.
The vol_id identified the volume.
The drive_id identifies the drive.
User Response: None. This message is informational only. If you continue experiencing problems with the drive or cartridge, provide this FSC to Oracle Support in order to help them diagnose the problem.
Duplicate label vol_id, with media domain and type media_domain_type, reported in the library in component component_id.
Explanation: The library reported that it contains two or more cartridges with the same label.
Variable:
The vol_id identifies the duplicate volume label.
The media_domain_type is the media domain immediately followed by the media type.
The component identifies the component type (ACS, CAP, cell, or drive).
The component_id identifies the component.
User Response: Please see message 2148.
Please eject the duplicate volumes with label vol_id via SLConsole and re-enter the correct volume.
Explanation: The library reported it contains two or more cartridges with the same label. Since ACSLS only supports unique labels (volume serial numbers), the duplicates must be ejected.
Variable: The vol_id identifies the duplicate volume label.
User Response: Use SLConsoles' recovery move function to eject all of the volumes reported in message 2147. Inspect them, and re-enter the correct volume.
proc_id: The configuration for ACS acs_id is out of date. The current configuration does not include component component_id with volume vol_id. Please update the configuration using Dynamic Config or acsss_config.
Explanation: The configuration for the ACS is out of date, while a volume is in a component that is currently not in the configuration, therefore, no longer accessible.
Variable:
The proc_id is the name of the procedure issuing the error message.
The acs_id identifies the ACS.
The component identifies the component type (cell or drive).
The component_id identifies the component.
The vol_id identifies the volume.
User Response: Either run the Dynamic Configuration utility to update the configuration for the ACS (config acs acs_id), or shutdown ACSLS and run acsss_config to reconfigure the ACS.
Lh error: proc_id: ACS acs_id configured to ACSLS with partition ID = partition_id, but the library is NOT partitioned.
Explanation: The ACS is attempting to connect to a partitioned library, but the library is not partitioned.
Variable:
The proc_id is the name of the procedure issuing the error message.
The acs_id identifies the ACS.
The partition_id is the partition to which the ACS is configured.
User Response: If partitioning is supposed to be disabled, run acsss_config to reconfigure the ACS to a non-partitioned library or to remove the ACS. Otherwise, enable partitioning on the library with the partition partition_id defined and reconnect.
Lh error: proc_id: ACS acs_id configured to ACSLS as NOT partitioned, but the library reports that this ACS is partitioned.
Explanation: The ACS is attempting to connect to a non-partitioned library, but the library is partitioned.
Variable:
The proc_id is the name of the procedure issuing the error message.
The acs_id identifies the ACS.
User Response: If partitioning is supposed to be enabled, run acsss_config to reconfigure the ACS to a defined partition or remove the ACS. Otherwise, disable partitioning on the library and reconnect.
Lh error: proc_id: ACS acs_id configured to ACSLS with partition ID = partition_id, but the library reports that this partition is not defined.
Explanation: The partition ID of the ACS is not a defined partition ID in the library.
Variable:
The proc_id is the name of the procedure issuing the error message.
The acs_id identifies the ACS.
The partition_id is the partition to which the ACS is configured.
User Response: Ensure that partitioning is enabled and the partition ID is defined on the library. If partition is enabled, but the partition ID is not defined, run acsss_config to reconfigure the ACS to the correct partition.
Lh error: proc_id: HLI Transmission header invalid for host/library compatibility level = compat_level.
Explanation: A communications error occurred between the ACSLS server and the library. When ACSLS communicates with a library via the Host/Library Interface (HLI), the transmission must match the compatibility level of the transmission. HLI libraries include the Sl3000 and SL8500.
Variable:
The proc_id is the name of the procedure issuing the error message.
The compat_level is the HLI compatibility level of the transmission.
User Response: Restart ACSLS. If the error reoccurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Lh error: proc_id: ACS acs_id already defined to partition defined_id; attempt to connect to partition new_id rejected.
Explanation: The ACSLS Library Handler received a connect request with a different partition ID than already defined for the ACS.
Variable:
The proc_id is the name of the procedure issuing the error message.
The acs_id identifies the ACS.
The defined_id is the partition ID already defined for a connection to the ACS.
The new_id is the new, rejected partition ID for the ACS.
User Response: if the problem is disruptive, complete the following:
Vary the ACS offline.
Vary all ports for the ACS offline.
Vary all ports for the ACS back online.
Vary the ACS online.
If the problem is still present, restart ACSLS.
If the problem reoccurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Lh error: proc_id: Port port_id already defined with port-name defined_name; attempt to connect to port-name new_name rejected.
Explanation: The ACSLS Library Handler received a connect request with a different port-name than already defined for the port.
Variable:
The proc_id is the name of the procedure issuing the error message.
The port_id identifies the port.
The defined_name is the port-name already defined to the port.
The new_name is the new, rejected port-name for the port.
User Response:
Vary the ACS offline.
Vary all ports for the ACS offline.
Vary all ports for the ACS back online.
Vary the ACS online.
If the problem is still present, restart ACSLS.
If the problem is still present, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
The reservation on CAP cap_id was overridden by the librarys' CLI or SLConsole.
Explanation: ACSLS received notification from library that an operator overrode the CAP reservation held by ACSLS for a CAP in a partitioned library.
Variable: The cap_id identifies the CAP.
User Response: Any enter or eject in progress has been terminated because the CAP reservation was overridden. If there are cartridges still in the CAP, they must be removed before the other partition can use the CAP. Please label these cartridges with the partition that they were being entered into or ejected from.
ACS acs_id is affected by a configuration, capacity, or partition change. Please run dynamic config to update the configuration of this ACS, and audit it.
Explanation: ACSLS received notification from the library that this ACS is affected by either a configuration, capacity, or partition change.
Variable:
The acs_id identifies the ACS.
The lsm_id is the LSM identifier.
User Response:
Run the Dynamic Configuration utility to update the configuration.
If the library configuration or capacity changed, update the configuration for the ACS (config acs acs_id) or LSM (config lsm_id).
Audit the affected ACS.
If tape drives were added to or removed from the Media Validation pool, use config drive <panel_id> to update the drive configuration.
Re-trying the mount of volume vol_id on drive drive_id using the volumes' new home cell.
Explanation: The original mount of the volume failed because the volume was not in its home cell. However, ACSLS was able to find the volume in another cell, and is thus reattempting the mount.
Variable:
The vol_id identifies the volume.
The drive_id identifies the drive.
User Response: None.
ACS acs_id: Library Recovery Started.
Explanation: The ACSLH (library handler process) has started the processing of library requests that were affected by a switch LMU, library IPL, or when communication with the library was lost and has been re-established.
Variable: The acs_id identifies the ACS.
User Response: None.
Port port_id lost communication with the library and has been varied offline. If communication is reestablished, the port will automatically be varied online.
Explanation: ACSLS cannot successfully communicate with the library over the port. The port will continually attempt to reestablish communication, and when successful, it will be varied back online.
Variable: The port_id identifies the port.
User Response:
Check that any cables used by the port are plugged in and operational.
Check that all hubs, switches, routers, etc. used by the port are operational.
Check that the physical devices on both ACSLS and the library are operational.
If the port does not come back online automatically after all checks have been made, vary the port offline and back online.
If the port still does not come online:
Vary the ACS offline.
Vary all ports for the ACS offline.
Vary all ports for the ACS back online.
Vary the ACS back online.
If the port is still offline, restart ACSLS.
If the port doesn't come online, restart the library.
If the problem reoccurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
ACS acs_id lost control of the library and has been varied offline. If control is reestablished, the ACS will automatically be varied to its previous state (previous_state).
Explanation: ACSLS can no longer control the library. All ports capable of controlling the library (a non-standby port) have either been varied offline or have lost communication with the library. When a controlling port is either varied online or reestablishes communication, the ACS automatically returns to its previous state. In a dual LMU configuration, standby port(s) may still be online and communicating. However, because standby ports cannot control the library, the ACS was varied offline.
Variable:
The acs_id identifies the ACS.
The previous_state is the desired state of the ACS before control was lost.
User Response: If a controlling port is varied offline, vary the port online. If all controlling port(s) are reconnecting, follow the Action Required section of Message 2160 to reconnect the port(s). If the ACS does not come back to its previous state automatically after a controlling port has come online:
Vary the ACS offline.
Vary all ports for the ACS offline.
Vary all ports for the ACS back online.
Vary the ACS back online/diagnostic.
If the ACS is still offline, restart ACSLS.
If the ACS does not come online, restart the library.
If the problem reoccurs, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Port port_id has reestablished communication with the library and has been varied online.
Explanation: ACSLS has successfully reestablished communication with the library over the port. The port is now online and operational.
Variable: The port_id identifies the port.
User Response: None.
ACS acs_id has reestablished control of the library and has been varied to its previous state (previous_state).
Explanation: ACSLS has reestablished control of the library, and the ACS has been varied to the desired state before control was lost. This occurred because a port capable of controlling the library (a non-standby port) either successfully reestablished communication with the library or was varied online.
Variable:
The acs_id identifies the ACS.
The previous_state is the desired state of the ACS before control was lost.
User Response: None.
Port port_id cannot be varied offline because the desired state for ACS acs_id is acs_state. Please vary ACS acs_id offline first.
Explanation: The attempt to vary the port offline failed because the port is either the last port online or the last port with a desired state of online, and the ACS needs to be online or diagnostic (previous acs_state). You cannot vary all of the ports of an ACS offline while the ACS is still needed to be online or diagnostic.
Variable:
The port_id identifies the port.
The acs_id identifies the ACS.
The acs_state is the desired state of the ACS.
User Response: To vary the port offline, either vary another port for the ACS online, or vary the ACS offline.
Cannot vary ACS acs_id new_state because no ports for this ACS have a desired state of online. Please vary a port for ACS acs_id online first.
Explanation: The attempt to vary the ACS online or diagnostic failed because no ports for the ACS are in an online state. You cannot vary an ACS online or diagnostic when no ports are online.
Variable:
The acs_id identifies the ACS.
The new_state is the requested state for the ACS.
User Response: To vary the ACS online or diagnostic, vary a port for the ACS online.
Desired state for component component_id set to new_state.
Explanation: The desired state for the component has successfully been updated and set to new_state in the database.
Variable:
The component identifies the component type (ACS or port).
The component_id identifies the component.
The new_state is the desired state for the component.
User Response: None.
Module: CAP cap_id is an Access Expansion Module (AEM) and should not be used for small enters and ejects. Therefore maximum CAP priority is one.
Explanation: An attempt was made to set the CAP priority of an AEM to a priority higher than one (1). AEMs are not designed for enters or ejects of small numbers of cartridges. To help prevent them from being automatically selected when the CAP ID is wild-carded with an asterisk or an LSM ID is specified, we do not allow AEMs to be set to a priority greater than 1.
Variable:
Module is the ACSLS module displaying this message.
The cap_id is the AEM specified in the set cap priority command.
User Response: Set the priority of an AEM to only zero or one. Please do not use AEMs for entering or ejecting small numbers of cartridges.
Limit of max_value variable_name exceeded.
Explanation: ACSLS detected a value which exceeded the maximum allowed for some program setting or variable. ACSLS processing will continue.
Variable:
The max_value is the maximum allowable value.
The variable_name is the program setting or variable.
User Response: Notify Oracle Support. (Although ACSLS processing continues, we want to know about this event.)
operation of volser on drive drive_id failed due to component status, and the time of timeout minutes was exceeded.
Explanation: ACSLS was unable to carry out a mount or dismount operation because a library component (ACS, LSM or drive) was unavailable, and the time limit for automatic retry was exceeded.
Variable:
The operation is the failing request type (mount or dismount).
The drive_id is the drive identifier.
The component is the library component which caused the request to fail.
The status is the status of the library component (currently offline or in recovery).
The timeout is the time limit (in minutes) which was exceeded. (See the MOUNT_RETRY_TIME_LIMIT dynamic variable.)
User Response: None. To retry the operation, make sure that any offline library components (ACS, LSM and drive) are made ready, available and online.
Volume vol_id, not in drive drive_id. ACSLS will recover cartridge automatically.
Explanation: An attempt was made to dismount a volume, but the volume was not in the drive. ACSLS will automatically try to find the cartridge in the library.
Variable:
The vol_id is the volume identifier of the volume.
The drive_id is the drive identifier.
User Response: None.
switch lmu for ACS acs_id not allowed because more than one SL8500 in ACS.
Explanation: A switch lmu command was issued for an ACS. However, the ACS includes multiple SL8500 libraries connected by pass-thru-ports. For SL8500 libraries, the switch lmu command is only supported against a single, standalone SL8500.
Variable: The acs_id is the ACS against which the switch lmu command was issued.
User Response: None.
switch lmu for ACS acs_id not allowed because ACS is partitioned.
Explanation: The switch lmu requests from a host, like ACSLS, are not supported for a partitioned library, because the switch would cause an outage for the other partition(s).
Variable: The acs_id is the ACS against which the switch lmu command was issued.
User Response: If you need to switch this library, use SLConsole.
More than max of max_drives_in_acsls drives in database, cannot re-configure.
Explanation: When trying to define or change your library hardware configuration with acsss_config, more than the maximum number of tape drives exist in all of the ACSs managed by this ACSLS system. The acsss_config terminates because it cannot support this many tape drives.
Variable: The max_drives_in_acsls is the maximum number of tape drives that acsss_config supports.
User Response: You can support this hardware configuration by either of the following options:
Manage separate ACSs (library complexes) with different ACSLS servers. max_drives_in_acsls supports at least 1500 tape drives (more than can be installed in over 20 SL8500 libraries).
Use the config acs new utility to configure a new ACS, and use config acs acs_id to re-configure an ACS.
Report this to Oracle Support so that the max_drives_in_acsls limit can be raised.
Restarting auto-enter for CAP cap_id.
Explanation: An automatic enter was restarted for the specified CAP.
Variable: The cap_id is the CAP for which the automatic enter was re-started.
User Response: You can proceed to enter cartridges through this CAP in the automatic enter mode.
Volume vol_id too long for Volume Access Control.
Explanation: ACSLS tried to check whether a volume was owned by a client under Volume Access Control. However, the specified volume has a volume ID longer than six characters. Volume Access Control only supports 6-character vol_ids.
Variable: The vol_id is the volume with a volume ID longer than six characters.
User Response: Please gather diagnostic information and report this to Oracle Support.
CAP cap_id: Not reserved for automatic enter.
Explanation: After a CAP was closed, it was determined that the CAP was not reserved for an automatic enter. The automatic enter request was terminated.
Variable: The cap_id is the CAP for which the automatic enter was started.
User Response: Vary the CAP offline force and back online, and then use set cap mode automatic to clean up the CAPs mode and status.
CAP cap_id: cap_size db_cap_size invalid for automatic enter.
Explanation: After a CAP was closed, it was determined that the size of the CAP recorded in the database was invalid. The automatic enter request was terminated.
Variable:
The cap_id is the CAP for which the automatic enter was started.
The db_cap_size is the size of the CAP recorded in the database. It was either zero or less, or larger than the largest CAP.
User Response: Update the CAPs configuration in the database to reset the CAPs' size.
Make sure all library components are ready and online.
Use either the dynamic config utility while ACSLS is up or acsss_config after stopping ACSLS.
If you are using dynamic config, use config acs acs_id to reconfigure an SL8500, and use config lsm lsm_id to reconfigure an SL3000 or 9310.
ACS acs_id: Called for circuit to standby or unknown LC.
Explanation: Tried to select a request for an active LC (Library Controller) for a circuit connected to a standby or unknown LC.
Variable: The acs_id identifies the ACS involved.
User Response: This is an internal error that should never occur. Collect diagnostic data and report this to Oracle Support.
Delete of current Xmit_active_q queue member failed.
Explanation: After selecting a request to be transmitted to the library, it could not delete this request from the queue of active requests.
Variable: None.
User Response: This is an internal error that should never occur. Please collect diagnostic data and report this to Oracle Support.
Get of Xmit_active_q queue member_id queue_member_id failed.
Explanation: Tried to get a request for an active LC (Library Controller) from the queue of active requests, but was unable to retrieve this queue member from the queue.
Variable: The queue_member_id identifies the internal queue member ID.
User Response: This is an internal error that should never occur. Please collect diagnostic data and report this to Oracle Support.
Delete of Xmit_active_q queue member_id queue_member_id failed.
Explanation: Tried to delete a request for an active LC (Library Controller) from the queue of active requests, but was unable to delete this queue member from the queue.
Variable: The queue_member_id identifies the internal queue member ID.
User Response: This is an internal error that should never occur. Please collect diagnostic data and report this to Oracle Support.
Module: Selected vol_type volume vol_id is an incompatible media type for drive drive_id.
Explanation: The library reported that the selected cleaning or scratch volume is incompatible with the tape drive. This should not happen. ACSLS automatically tries to select another cleaning or scratch cartridge and mount it.
Variable:
The vol_type is cleaning or scratch.
The vol_id is the volume identifier of the volume.
The drive_id is the drive identifier.
User Response: Eject the cartridge reported in the message and examine it for problems. This includes examining the cartridge's label and barcode. Make sure that the library firmware supports the media and tape drive.
Cannot create group acsdb.
Explanation: This error can occur only while installing the product on an AIX operating system. The installation program creates the Unix group named acsdb. It calls the Unix command mkgroup to create the group. This error is logged if the mkgroup command fails. Group ID # 106 should be available.
Variable: None.
User Response: Reinstall ACSLS after the problem has been corrected.
Cannot create acsdb user.
Explanation: This error can occur only while installing the product on an AIX operating system. The installation program creates the UNIX user named acsdb. It calls the UNIX command mkuser to create the group. This error is logged if the mkuser command fails. User ID # 11 should be available.
Variable: None.
User Response: Reinstall ACSLS after the problem has been corrected.
Group file update (acsdb) failed: updates discarded.
Explanation: This error can occur only while installing the product on an Oracle's Solaris operating system. The installation program creates the UNIX group named acsdb. If the group name already exists, it tries to update the entry. This error is logged if the update fails.
Variable: None.
User Response: Reinstall ACSLS after the problem has been corrected.
Group file move (acsdb) failed: updates discarded.
Explanation: This error can occur only while installing the product on a Solaris operating system. The installation program creates the UNIX group named acsdb. It tries to move the previous version of group file. This error is logged if the move fails.
Variable: None.
User Response: Reinstall ACSLS after the problem has been corrected.
Insufficient disk space available in disk. Need needed_space KB. Have available_space KB. You must make at least needed_space KB available in disk before installing ACSLS database.
Explanation: The installation program verifies the available disk space before commencing the installation. This message is logged if where the ACSLS disk is being installed does not have enough space to install ACSLS database software.
Variable:
The disk on which the ACSLS product is being installed.
The needed_space is the disk space needed to install the ACSLS database.
The available_space indicates the space available on the disk.
User Response: Make space in the chosen directory by deleting files. Choose another directory that has more disk space, then reinstall ACSLS or install a larger disk.
ACSLS database installation failed.
Explanation: This error is logged when the ACSLS database software installation fails. The cause can be one or several of the following:
The directory chosen to install acsdb is not writable.
The disk specified for backups had insufficient space.
Initialization of the shared memory failed.
Variable: None.
User Response:
The directory chosen to install ACSLS database is not writable. Choose a directory that has write access and reinstall ACSLS.
If the installation is being done using tapes, the tape is bad and the extraction failed. Replace the media and reinstall ACSLS.
If the disk specified for backups had insufficient space on it, increase the available disk space and reinstall ACSLS.
If initialization of the shared memory failed, reinstall ACSLS.
Variable: The dev is the backup directory that is being registered as a backup device.
User Response: Check to see whether the directory exists. If not, then create one with the same name and retry installation. If it exists, the permission should be 664. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error in labelling dev.
Explanation: During installation, the install program creates backup volumes. This message is logged when this process fails. This can happen if a volume with the same name already exists.
Variable: The dev is the backup directory which is associated with the backup volume.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error in mounting dev.
Explanation: During installation, the install program creates and mounts backup volumes. This message is logged when mounting a backup device fails. This can happen for the following reasons: the device does not exist or the backup volume with which the device is associated does not exist.
Variable: The dev is the directory that is being mounted.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error in creating new devices.
Explanation: During installation of second disk, the backup directories are shifted to directories in the second disk. This message is logged when this process fails.
Variable: None.
User Response: Please refer to the sd_event.log and see the error message number logged before this error number in order to know the exact reason for failure. One of the following errors may be the reason for failure. Please refer to the following error numbers for more details: 1581, 1516, 1569, 2227, 2229, 2230, 2216, 2217, and 2218. Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Secondary disk already installed.
Explanation: This message is logged while doing the second disk installation if a secondary disk has already been installed.
Variable: None.
User Response: When this error occurs, a second disk is already installed and no action is required.
ACSLS control files backup successfully completed.
Explanation: ACSLS control file backup was successful.
Variable: None.
User Response: None.
Error in turning mirror off for rootdbs.
Explanation: This message is logged while de-installing the second disk.
Variable: None.
User Response: Contact your System Administrator or collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
Second disk de-installation completed successfully.
Explanation: This message is logged when second disk deinstallation is completed successfully.
Variable: None.
User Response: This message does not appear if the installation fails.
Error in unmounting dev.
Explanation: This message is logged when an error occurs while installing or de-installing the second disk. Also, the dismount fails if the backup device is in use by a backup or restore session.
Variable: The dev is the directory being dismounted.
User Response:
Check if any backup process is running. If so, wait until the backup is completed.
If the error was encountered while installing the second disk option, reinstall sd_mgr.sh.
If the error was encountered while de-installing the second disk option, reinstall sd_mgr.sh.
Unable to mirror dbspace on Secondary disk.
Explanation: As a part of the second disk installation, ACSLS mirrors the database on to the second disk in order to provide additional security for your data against failures. This message is logged if the process of mirroring fails.
Variable: None.
User Response: Make sure the path given for the second disk is a valid one. Make sure the proper permissions (667) are set for the mirror dbspace on the second disk. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Unable to remove the device dev.
Explanation: During installation of a second disk, the backup directories are shifted to directories in the second disk. In this process, the devices used with the primary disk are removed. This message is logged when this process fails.
Variable: The dev is the directory being removed.
User Response:
Check if any backup process is running. If so, wait until the backup is completed.
If the error was encountered while installing the second disk option, reinstall sd_mgr.sh.
If the error was encountered while de-installing the second disk option, reinstall sd_mgr.sh.
program: Cannot set ODBC driver version. Status code (error_code).
Explanation: An internal error happened while ACSLS was trying to connect to the database.
Variable:
The program is the name of the source file where the error was encountered.
The error_code is the error code encountered by the application on return from the SQLSetEnvAttr ODBC function.
User Response: Reboot the server and retry (suspecting memory to be the reason).
ACSLS database backup started.
Explanation: Database backup process started.
Variable: None.
User Response: None.
ACSLS database backup successfully completed.
Explanation: Successfully completed the backup of the database.
Variable: None.
User Response: None.
EXEC SQL delete from audittable.
Explanation: An attempt to delete the rows from the audit table has failed.
Variable: None.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Unable to configure volume backup data_volume.
Explanation: As a part of the manual backup, the backup files are archived to a tar file. During this process, the backup devices are configured to disallow backups until the archival is complete. This message is logged if an error occurs while configuring the backup devices.
Variable: The backup data_volume is the backup volume that could not be configured. Volume names suffixed with pri_ indicate that they are primary disk volumes. Similarly, volume names suffixed with sec_ indicate that they are secondary disk volumes.
User Response: Please log out then log in as acsss and retry the second disk installation or deinstallation.
Cannot remove the directory directory.
Explanation: Deletion of a directory may have failed due to access permission problems.
Variable: The directory is the directory being deleted.
User Response: Ensure that you are logged in as the correct user to execute this utility. Check the access permissions for the directory.
Failed to add necessary CRON entry for automatic backup.
Explanation: The automatic backup configuration script registers the periodic backup event with the Operating System Scheduler. This error is logged when the registration failed.
Variable: None.
User Response: Contact your System Administrator or collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
ACSLS database recovery successfully completed. Database has been restored to the point of the specified backup.
Explanation: This message is logged after successfully restoring from a previous local disk backup.
Variable: None.
User Response: None.
ACSLS control files backup failed.
Explanation: The backup of the ACSLS control files failed.
Variable: None.
User Response: None.
Disk is percentage full, please decrease the database backup retention period to free disk space.
Explanation: The disk used for backup is running out of space. If expired volumes are not removed, there is a very high possibility of the backup disk overflowing. As a result, the automatic backup could fail to back up your data.
Variable: The percentage is the percentage indicating the amount of the disk space already used.
User Response:
Run the acsss_config script and select option 5: Set automatic backup parameters.
Reply n for the prompt Would you like to modify the automatic backup settings? (y or n):
Using the next prompt, set the retention period to a lower value. This setting automatically deletes expired backups, thereby releasing locked up disk space.
Unexpected error occurred in automatic configuration settings.
Explanation: The script that allows the user to configure the automatic backup parameters has failed. The failure may be due to the following reasons:
The variable $ACS_HOME points to an incorrect directory.
This script depends upon another script $ACS_HOME/.acsss_env. That script is missing.
Could not find script fix_autobkup_cron.sh.
The configuration program registers your auto backup settings with the Operating System Scheduler. This process failed.
Variable: None.
User Response: Please log out of the session and log in again. ACSLS reloads all of the variables. If the error occurred because the environment variables were altered accidentally, the reloading will set it right. Reinstall ACSLS if any product files are missing. Execute the script acsss_config to configure the auto-backup parameters.
Expired backup files could not be removed.
Explanation: ACSLS removes expired backup files prior to initiating a backup in order to avoid overfilling the backup disk. This message indicates that the recycling of the expired files could not be completed successfully.
This can happen if:
The environment file $ACS_HOME/.acsss_env is not found.
The environment variable RETENTION_PERIOD is not set.
The variable $ACSDB_BACKUP_DIR was altered or erased.
The variable $ACSDB_BACKUP_DIR points to an incorrect directory.
There is no permission to delete files in the directory pointed to by $ACSDB_BACKUP_DIR.
User Response:
Log out of the session and log in again with the correct user ID. ACSLS reloads all the variables. If the error occurred because the environment variables got altered accidentally, the reloading would set it right.
Reinstall ACSLS if any product files are missing.
Contact your System Administrator or collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Recycle of expired files completed.
Explanation: Prior to initiating a backup in order to avoid overfilling the backup disk, ACSLS removes expired backup files. This message indicates that the recycling of the expired files was completed successfully.
Variable: None.
User Response: None.
ACSLS backup completed successfully.
Explanation: ACSLS backup has been completed successfully.
Variable: None.
User Response: None.
ACSLS control files backup started.
Explanation: The backup of the control files used by the ACSLS product is being started.
Variable: None.
User Response: None.
Failed to recycle expired files.
Explanation: An internal error occurred while trying to recycle expired backup files.
Variable: None.
User Response: None.
Writing ACSLS backup file to target location.
Explanation: Creating final tar for the backup.
Variable: None.
User Response: None.
Cartridge stuck in the in-transit cell. Please vary LSM lsm_id offline and back online again to recover the cartridge.
Explanation: A cartridge is stuck in the in-transit cell of LSM with identifier lsm_id.
Variable: The lsm_id is the LSM identifier.
User Response: Vary the LSM specified in the message offline, and back online to recover the cartridge.
LSM lsm_id in maintenance mode.
Explanation: The LSM with the specified lsm_id is in maintenance mode.
Variable: The lsm_id is the LSM identifier.
User Response: Record any status information displayed on the Library. IPL the LSM. In ACSLS, vary the LSM online. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Micro-code had been changed in LSM lsm_id.
Explanation: The microcode level for the LSM (with identifier lsm_id) has been changed
Variable: The lsm_id is the LSM identifier.
User Response: None.
Pass-thru port inoperative in LSM lsm_id.
Explanation: The pass-thru port in LSM with identifier lsm_id is inoperative.
Variable: The lsm_id is the LSM identifier.
User Response: Record any status information displayed on the Library. IPL the LSM. In ACSLS, vary the LSM online. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
LSM lsm_id Not Ready. Manual Intervention Required.
Explanation: The LSM with identifier lsm_id is not ready. Possible reasons are that a door is open or a cartridge is stuck in the LSM hand.
Variable: The lsm_id is the LSM identifier.
User Response: Check the LSM hand and manually remove the cartridge. Be sure that the LSM door is closed.
Cartridge stuck in pass-thru port. Please vary any LSM in ACS acs_id offline and back online again to recover the cartridge.
Explanation: A cartridge is stuck in the pass-thru port of ACS acs_id. Vary any LSM in the ACS specified in the message offline and back online to recover the cartridge.
Variable: The acs_id is the ACS identifier.
User Response: Vary any LSM in the ACS specified in the message offline and back online to recover the cartridge.
LSM lsm_id could not recover volume vol_id.
Explanation: One of the LSMs could not recover a cartridge.
Variable:
The lsm_id is the LSM identifier.
The vol_id is the Volume identifier of the cartridge.
User Response: None. The cartridge will probably be recovered by the other LSM of the L700e pair while coming online.
LSM lsm_id received Unit Attention Sense: sense_code (sense_desc).
Explanation: A SCSI device has returned a Sense Code for the LSM lsm_id.
Variable:
The lsm_id is the LSM identifier.
The sense_code is the Sense Code returned by the SCSI device.
The sense_desc is a brief description of the sense code returned.
User Response: None.
LSM lsm_id received Sense: sense_code (sense_desc).
Explanation: A SCSI device has returned a Sense Code for the LSM lsm_id.
Variable:
The lsm_id is the LSM identifier.
The sense_code is the Sense Code returned by the SCSI device.
The sense_desc is a brief description of the sense code returned.
User Response: Record any status information displayed on the Library. IPL the LSM. In ACSLS, vary the LSM online. If the problem persists, call Oracle Support
DB status [err_num] detected on delete from clienttable.
Explanation: An attempt to delete a client record from the database has failed.
Variable: The err_num is the error number.
User Response: Restart the application server and see if the problem persists. If it does, restart the database and see if the problem persists. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support").and contact Oracle Support.
Exec SQL lock timeout on delete from clienttable.
Explanation: An attempt to delete a locked client record from the database has failed.
Variable: None.
User Response: Restart the application server and see if the problem persists. If it does, restart the database and see if the problem persists. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Unexpected resource type rsc_type and resource status rsc_status.
Explanation: An unexpected match of resource type and resource status is detected.
Variable:
The rsc_type is the value of resource type.
The rsc_status is the value of resource status.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Status of lib_cmpnt cmpnt_id is changed to status.
Explanation: Status of a library component, such as LSM, CAP or DRIVE with an identifier cmpnt_id, such as 0,0(lsm_id) or 0,0,0(cap_id) or 0,0,7,1(drive_id) is changed to status.
Variable:
The lib_cmpnt is a library component type like that of the following: LSM, DRIVE, or CAP.
The cmpnt_id is the identifier of a library component, such as 0,0(lsm_id), 0,0,0(cap_id), or 0,0,7,1(drive_id).
The status is the new status value.
User Response: None.
Invalid lib_cmpnt cmpnt_id received in a message from module_type; dropping message.
Explanation: This message indicates that acsmon received a message that included an invalid component identifier. The message is dropped, and normal processing continues.
Variable:
The lib_cmpnt is a library component type, like that of the following: LSM, DRIVE, or CAP.
The cmpnt_id is the identifier of a library component, such as 0,0(lsm_id), 0,0,0(cap_id), or 0,0,7,1(drive_id).
The module_type is the name of the module that sent the message
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Serial number of lib_cmpnt cmpnt_id changed to serial_num.
Explanation: This message is to indicate that there is a serial number change for a library component, such as LSM or DRIVE and with an identifier cmpnt_id, such as 0,0(lsm_id) or 0,0,7,1(drive_id).
Variable:
The lib_cmpnt is a library component type, such as LSM, DRIVE or CAP.
The cmpnt_id is the identifier of a library component, such as 0,0(lsm_id) or 0,0,7,1(drive_id).
The serial_num is the new serial number..
User Response: None.
EXEC SQL failed to create table_name, error = err_num
Explanation: An ODBC call to prepare an SQL statement for creating a table table_name has failed.
Variable:
The table_name is table name to be created.
The err_num is the error number returned by ODBC.
User Response: Restart the database and see if the problem persists. If it does, contact your System Administrator.
DB status [err_num] detected on delete for client id client_id
Explanation: An attempt to delete a client record from the database has failed.
Variable:
The err_num is the error number.
The client_id is the identifier of the client to be deleted.
User Response: Restart the application server and see if the problem persists. If it persists, restart the database and see if the problem persists. If it does, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
EXEC SQL lock timeout on delete from clienttable where client_id = clnt_id
Explanation: An ODBC call to prepare an SQL statement for deleting a client record from clienttable has failed.
Variable: The clnt_id is an identifier of the client to be deleted.
User Response: Restart the application server and see if the problem persists. If it persists, restart the database and see if the problem persists. If it does, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL delete from clienttable failed, where client_id = clnt_id
Explanation: An attempt to delete a locked client record from clienttable has failed.
Variable: The clnt_id is the identifier of the client to be deleted.
User Response: Restart the application server and see if the problem persists. If it persists, restart the database and see if the problem persists. If it does, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL select client_id clnt_id from clienttable failed.
Explanation: An ODBC call to prepare an SQL statement for selecting a client record(s) from clienttable has failed.
Variable: The clnt_id is the identifier of the client to be selected.
User Response: Restart the application server and see if the problem persists. If it persists, restart the database and see if the problem persists. If it does, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL failed to open cursor.
Explanation: An ODBC call to prepare an SQL statement for opening a cursor has failed.
Variable: The cursor is the database handle for executing SQL statement.
User Response: The application has to be re-started. Contact your System Administrator.
Starting automatic backup to local disk.
Explanation: This message is displayed when you opt not to take backup on to a tape while exiting from rdb.acsss. In this case, an automatic backup to a local disk is triggered.
Variable: None.
User Response: None.
ACSSS services are running. To restore the database you must first shutdown ACSLS by running 'acsss db'.
Explanation: The database restore utility discovered that ACSSS services were running.
Variable: None.
User Response: You must bring down all ACSLS services except acsdb before you can restore the ACSLS database. To do this, run acsss db.
ACSLS is running. To stop the database, ACSLS must first be shutdown using 'idle' and 'kill.acsss'. Exiting.
Explanation: This error is logged when you try to stop the database while ACSLS is running. This is not allowed since the application communicates extensively with the database. The ACSLS application must be shut down prior to shutting down the database.
Variable: None.
User Response: Stop ACSLS by executing the commands idle and kill.acsss. Shut down the database server using db_command stop.
ACSLS is running. To run rdb.acsss, ACSLS must first be shutdown using 'idle' and 'kill.acsss'. Exiting.
Explanation: This message is logged when you try to recover the database using rdb.acsss while the ACSLS application is running.
Variable: None.
User Response: Stop ACSLS by executing the commands idle and kill.acsss. Shut down the database server using db_command stop.
getenv failed for \"LSPID_FILE\" in mod_id at line line_number.
Explanation: An attempt to get the environment variable LSPID_FILE, which would indicate ACSLS is running, has failed.
Variable:
The mod_id is the name of the module issuing the error message.
The line_number is the location in the ACSLS code where the error was detected.
User Response: None. The program exits after issuing the message.
stat failed for ${LSPID_FILE} in mod_id at line line_number. errno is error_no: error
Explanation: An attempt to locate the /tmp/acsss.pid file has failed. ACSLS can not run properly without this process.
Variable:
The mod_id is the name of the module issuing the error message.
The line_number is the location in the ACSLS code where the error was detected.
The error_no is the error number returned if the /tmp/acsss.pid file doesn't exist
The error is the text of the error message for error_no.
User Response: None. The program exits after issuing the message.
ACSLS must be running to execute command
Explanation: The command that was entered can not run without an active ACSLS session.
Variable: The command is the command that was entered by the user.
User Response: None. The program exits after issuing the message.
Volume found in the library. Unable to delete, use EJECT.
Explanation: A manual volume delete request failed because the volume to be deleted was located by the Cartridge Recovery component. Manual volume delete can not be used to delete a verifiability present volume in an active LSM. In such a case, EJECT should be used to remove tapes from an LSM.
Variable: None.
User Response: None. The program exits after issuing the message.
Cartridge Recovery could not examine all recorded locations for this volume.
Explanation: The Cartridge Recovery component was unable to catalog a library location where the requested volume may reside. This can be due to an offline LSM or a non-communicating drive. User confirmation is required to delete these volumes. This message is issued in conjunction with MSG 2308 below. This message is suppressed and confirmation assumed if the -n (no_confirm flag) was included in the original manual volume delete message.
Variable: None.
User Response: None. The program exits after issuing the message.
Do you really want to delete volume vol_id from the database? [yes|no]
Explanation: A request for user confirmation is issued whenever the Cartridge Recovery component can not examine all possible library locations for the volume (see MSG 2307). This message is suppressed and confirmation assumed if the -n (no confirm flag) was included in the original manual volume delete message.
Variable: The vol_id is the volume serial number requested for deletion.
User Response: None.
md_proc_init failure: status = status.
Explanation: The function to register this process for error-logging failed.
Variable:
The mod_proc_init is the name of the module issuing the error message.
The status is the text of the status value returned from cl_ipc_create().
User Response: None. The program exits after issuing the message.
mod_id: atexit failure: errno = error_no: error_msg.
Explanation: This message is issued for a failed attempt to register the database disconnect or ipc destroy wrapper functions to be executed at the time the manual volume delete process exits.
Variable:
The mod_id is the name of the module issuing the error message.
The error_no is the error number returned if the /tmp/acsss.pid file doesn't exist.
The error_msg is the text of the error message that corresponds with error_no.
User Response: None. The program exits after issuing the message.
mod_id: cl_db_connect failure: status = status.
Explanation: The program was unsuccessful in connecting to the database.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_db_connect().
User Response: None. The program exits after issuing the message.
mod_id: cl_vol_read failure: status = status
Explanation: An attempt to read a volume record from the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_vol_read.
User Response: None. The program exits after issuing the message.
mod_id: cl_cel_read failure: status = status.
Explanation: An attempt to read a cell record from the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_cel_read.
User Response: None. The program exits after issuing the message.
mod_id: cl_lsm_read failure: status = status
Explanation: An attempt to read an LSM record from the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_lsm_read.
User Response: None. The program exits after issuing the message.
mod_id: cl_drv_read failure: status = status.
Explanation: An attempt to read a drive record from the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_drv_read.
User Response: None. The program exits after issuing the message.
mod_id: cl_loc_read failure: status = status.
Explanation: An attempt to read a lock record from the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_loc_read.
User Response: None. The program exits after issuing the message.
mod_id: cl_vac_read failure: status = status.
Explanation: An attempt to read a volume access control record from the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_vac_read.
User Response: None. The program exits after issuing the message.
mod_id: cl_cel_destroy failure: status = status.
Explanation: An attempt to delete a volume record from the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_cel_destroy.
User Response: None. The program exits after issuing the message.
mod_id: cl_cel_write failure: status = status.
Explanation: An attempt to update a cell record on the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_cel_write.
User Response: None. The program exits after issuing the message.
mod_id: cl_db_disconnect failure: status = status.
Explanation: An attempt to disconnect from the database failed.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_db_disconnect.
User Response: None. The program exits after issuing the message.
mod_id: Cartridge Recovery failure: status = status
Explanation: The Cartridge Recovery (ACSCR) component returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from the Cartridge Recovery component (ACSCR).
User Response: None. The program exits after issuing the message.
mod_id: cl_ipc_write failure: status = status.
Explanation: The cl_ipc_write function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_ipc_write.
User Response: None. The program exits after issuing the message.
mod_id: cl_ipc_read failure: status = status.
Explanation: The cl_ipc_read function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_ipc_read.
User Response: None. The program exits after issuing the message.
mod_id: cl_ipc_destroy failure: status = status.
Explanation: The cl_ipc_destroy function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_ipc_destroy.
User Response: None. The program exits after issuing the message.
mod_id: cl_qm_init failure: status = status.
Explanation: The cl_qm_init function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The status is the text of the status value returned from cl_qm_init.
User Response: None. The program exits after issuing the message.
mod_id: cl_qm_qcreate failure: queue = queue_name
Explanation: The cl_qm_create function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The queue_name is the name of the internal queue for which the failure occurred.
User Response: None. The program exits after issuing the message.
mod_id: cl_qm_mcreate failure: queue = queue_name
Explanation: The cl_qm_mcreate function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The queue_name is the name of the internal queue for which the failure occurred.
User Response: None. The program exits after issuing the message.
mod_id: cl_qm_maccess failure: member = member_id
Explanation: The cl_qm_maccess function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The member_id is the identifier of the queue member for which the failure occurred.
User Response: None. The program exits after issuing the message.
mod_id: cl_qm_mlocate failure: member = member_id
Explanation: The cl_qm_mlocate function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The member_id is the identifier of the queue member for which the failure occurred.
User Response: None. The program exits after issuing the message.
mod_id: cl_qm_mdelete failure: member = member_id.
Explanation: The cl_qm_delete function returned an error.
Variable:
The mod_id is the name of the module issuing the error message.
The member_id is the identifier of the queue member for which the failure occurred.
User Response: None. The program exits after issuing the message.
Unreadable label found in location_type location_id: logged as vol_id
Explanation: In the course of performing Cartridge Recovery, a cartridge with an unreadable label was discovered. No cartridge with a virtual label was recorded in this location.
Variable:
The location_type is the type of location (cell, drive) in which the unreadable label was detected.
The location_id is the specific identifier of the location (cell_id or drive_id).
The vol_id is a generated volume identifier of the form UL@nnn where nnn begins with 001 when Cartridge Recovery is initialized and is incriminated each time an unreadable cartridge is reported. If the location is a drive, this volume identifier is recorded in the drive record.
User Response: The unreadable cartridge is not ejected by Cartridge Recovery. If the location is a drive, the cartridge will be processed during dismount. If the location is a cell, physical removal of the unreadable cartridge may be required. An audit can be used to check the cell, and will result in ejection.
Duplicate label found in location_type location_id: label=vol_id logged as dup_id
Explanation: In the course of performing Cartridge Recovery, a cartridge was encountered which appears to be a duplicate. The cartridge was found unexpectedly while looking for some other cartridge, and when the recorded home cell for the unexpected cartridge was checked, the home cell contained what is presumed to be the original cartridge.
Variable:
The location_type is the type of location (cell, drive) in which the unreadable label was detected.
The location_id is the specific identifier of the location (cell_id or drive_id).
The vol_id is the volume identifier of the cartridge for which a duplicate was found. If the encountered label was unreadable, this may be a virtual label.
The dup_id is a generated volume identifier of the form DL@nnn where nnn begins with 001 when Cartridge Recovery is initialized and is incremented each time a duplicate cartridge is reported. If the location is a drive, this volume identifier is recorded in the drive record.
User Response: The duplicate cartridge is not ejected by Cartridge Recovery. If the location is a drive, the cartridge will be processed during dismount. If the location is a cell, physical removal of the duplicate cartridge may be required.
Note:
Theeject command cannot be used to remove the cartridge, since it would eject the original rather than the duplicate, and no record exists for the generated volume identifier.Found volume vol_id in location will check home_cell_id when lsm lsm_id comes online.
Explanation: In the course of performing Cartridge Recovery, a cartridge was encountered unexpectedly in a storage cell. When attempting to check the recorded home cell for that cartridge, the home LSM was found to be offline or inaccessible. The cartridge may be a duplicate, but that could not be determined at this time. The recorded home cell is marked as reserved, which will cause it to be checked when the LSM comes online. The volume record is updated to reflect the new location in which it was found.
Variable:
The vol_id is the volume identifier of the cartridge.
The location is the location in which the cartridge was found.
The home_cell_id is the recorded home cell for the cartridge.
The lsm_id is the identifier of the LSM containing the recorded home cell.
User Response: None. When the LSM containing the old home cell comes online, the cell will be checked and its status corrected.
Volume vol_id missing, home cell was cell_id, drive was drive_id, unable to examine location
Explanation: This tape cartridge was not found where ACSLS expected it, but either the home cell or the drive couldn't be examined during the recovery process. The volume record will remain in the database with a missing status until ACSLS can examine all recorded locations.
Variable:
The vol_id is the volume identifier of the missing cartridge.
The cell_id is the home cell recorded for the cartridge.
The drive_id is the drive recorded for the cartridge.
The location is the location (either cell, drive, or cell and drive) that ACSLS could not examine.
User Response: At least one recorded location could not be examined. ACSLS will automatically attempt to recover the cartridge when an LSM comes online. The missing status will be resolved when:
The cartridge is found in one of the recorded locations by Cartridge Recovery. The volume record will be updated to reflect the location of the cartridge.
Cartridge Recovery is able to check all recorded locations, and the cartridge is not found. In this case, the volume record will be deleted.
Manual Volume Delete is used to delete the volume record from the database.
Volume vol_id was not found and will be deleted.
Explanation: This tape cartridge was not found in any location recorded by ACSLS. The volume record will be deleted from the database. This message will be followed by a 1054 I message that specifies the home cell and drive id which were recorded for this volume.
Variable: The vol_id is the volume identifier of the cartridge that will be deleted.
User Response: None.
mod_id: Invalid volume id vol_id
Explanation: This messages is issued when an invalid volume ID is entered.
Variable:
The mod_id is the name of the module issuing the error message.
The vol_id is the identifier of the volume that was found.
User Response: Reenter the command with the correct volume ID.
Volume vol_id: Media type mismatch, recorded as media_type, read as media_type.
Explanation: The media type of the specified volume is recorded differently in the database than what was returned from a physical catalog of the volume's location. This could possibly indicate that a label has fallen off.
Variable:
The vol_id is the volume serial number found by Cartridge Recovery.
The media_type is the volumes' media type designator.
User Response: Cartridge may need to be relabeled. Operator intervention may be necessary.
surr_main (PID #####): Unable to set SO_REUSEADDR on SURROGATE LISTENER socket NNNNN
Explanation: The Surrogate main routine was unable to set the SO_REUSEADDR option on the socket using the setsockopt() system call. This option allows the socket at that port number to be reused if it still exists as can be the case if ACSLS is restarted soon after it was stopped. IPC Surrogate terminates.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the port number on which the Surrogate is trying to set the option.
User Response:
Look for associated errors that may indicate why the setsockopt call failed.
Kill the ACSLS system using the kill.acsss command.
Next, kill any additional ”zombie” ACSLS processes (using a ps | grep acs).
See if the socket is in use (possibly by another process) with a netstat -a | grep NNNNN where NNNNN is the socket number shown in the error message.
If the socket is in use, wait for a few minutes to see if the socket eventually times out. Then restart ACSLS with the rc.acsss command. It may be necessary to reboot the ACSLS host to release any hung sockets.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
surr_main (PID #####): Unable to bind SURROGATE LISTENER socket NNNNN
Explanation: The Surrogate main routine was unable to bind the main listener socket that it uses to accept requests from the Gateway on using the bind() system call. Each Surrogate has a unique port number it is trying to bind to. IPC Surrogate terminates.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the port number to which the Surrogate is trying to bind().
User Response:
Look for associated errors that may indicate why the bind() call failed.
Kill the ACSLS system using the kill.acsss command.
Next, kill any additional ”zombie” ACSLS processes (using a ps | grep acs).
See if the socket is in use (possibly by another process) with a netstat -a | grep NNNNN where NNNNN is the socket number shown in the error message.
If the socket is in use, wait for a few minutes to see if the socket eventually times out. Then restart ACSLS with the rc.acsss command. It may be necessary to reboot the ACSLS host to release any hung sockets.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
surr_main (PID #####): Listen error on SURROGATE LISTENER socket NNNNN
Explanation: The Surrogate main routine was unable to complete a listen() system call on the main listener socket that it uses to accept requests from the Gateway. Each Surrogate has a unique port number to which it is trying to listen(). IPC Surrogate terminates.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the port number on which the Surrogate is trying to listen().
User Response:
Look for associated errors that may indicate why the listen() call failed.
Kill the ACSLS system using the kill.acsss command.
Next, kill any additional ”zombie” ACSLS processes (using a ps | grep acs).
See if the socket is in use (possibly by another process) with a netstat -a | grep NNNNN where NNNNN is the socket number shown in the error message.
If the socket is in use, wait for a few minutes to see if the socket eventually times out. Then restart ACSLS with the rc.acsss command. It may be necessary to reboot the ACSLS host to release any hung sockets.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
PID ##### surr_main (PID #####): Surrogate listening on port NNNNN SURROGATE_QUEUE_AGE is set to NN minutes SURROGATE_TIMEOUT is set to NNN seconds TRACING is <ON/OFF> QUEUE currently has NN active requests.
Explanation: This message indicates what socket port the Surrogate is listening on to receive ACSLS requests from a Library Management Gateway system. It is issued when the Surrogate starts and has successfully created, bound, and is actively listening on the socket. Also shown are the current values that the program is using for SURROGATE_QUEUE_AGE and SURROGATE_TIMEOUT. These two variables and the SURROGATE_PORT are dynamic environment variables set in the acsss_config program. Also displayed is whether program tracing is set ”on” or ”off”. Finally, the number of requests that are currently on the queue is shown. This message is also displayed when the program receives a SIGHUP signal (such as, kill -hup #####). The Surrogate continues running.
Variable:
The ##### is the Process ID of the Surrogate issuing the message.
The NNNNN is the port number on which the Surrogate is listening.
The NN is the number of minutes for which the SURROGATE_QUEUE_AGE is set.
The NNN is the number of seconds until SURROGATE_TIMEOUT. takes effect.
The NN is the number of active requests in the QUEUE
User Response: None.
surr_main (PID #####): Socket initialization failed for SURROGATE LISTENER socket NNNNN; rc=XX
Explanation: The Surrogate main routine was unable to complete a listen() system call on the main listener socket that it uses to accept requests from the Library Management Gateway. Each Surrogate has a unique port number on which it is trying to listen(). IPC Surrogate terminates.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the port number on which the Surrogate is trying to listen.
The XX is the return code from the listen() call.
User Response: This could be a possible hardware or network failure.
Look for associated errors that may indicate why the listen() call failed.
Kill the ACSLS system using the kill.acsss command.
Next, kill any additional ”zombie” ACSLS processes (using a ps | grep acs).
See if the socket is in use (possibly by another process) with a netstat -a | grep NNNNN where NNNNN is the socket number shown in the error message.
If the socket is in use, wait for a few minutes to see if the socket eventually times out. Then restart ACSLS with the rc.acsss command. It may be necessary to reboot the ACSLS host to release any hung sockets.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
surr_handler (PID #####): Due to above error, packet is dropped & GATEWAY CONNECTED socket (NNNNN) closed.
Explanation: The Surrogate handler routine encountered an error earlier, which rendered the current ACSLS request unable to run to completion. Consequently, the Surrogate is forced to abort that particular request packet and close the socket that it was using to communicate with the Library Management Gateway servlet (the GATEWAY CONNECTED socket). This error is not considered fatal to the Surrogate. PC Surrogate closes the socket, removes the queue entry, and continues running.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the socket number that the Surrogate has closed.
User Response:
Look for an error message preceding this one that caused the packet to be dropped and socket closed.
Look for other associated errors on the Gateway, Adapter, and client machines.
Try to identify the ACSLS command that was being sent from the originating client system.
If possible, re-send the offending command with tracing turned on for the Surrogate, Gateway, and Adapter.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
surr_handler (PID #####): Write of ipc data to GATEWAY CONNECTED socket NNNNN failed..
Explanation: The Surrogate handler routine encountered an error trying to write data to the socket connected to the Library Management Gateway servlet (GATEWAY CONNECTED socket). The write() system call failed. This may have occurred because the socket prematurely closed before all the data was written. IPC Surrogate terminates.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the socket number to which the Surrogate was trying to write.
User Response: This could be a possible hardware or network failure.
Look for associated error message preceding this one that may indicate the cause.
Look for other associated errors on the Gateway, Adapter, and client machines.
Try to identify the ACSLS command that was being sent from the originating client system.
If possible, re-send the offending command with tracing turned on for the Surrogate, Gateway, and Adapter.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
surr_handler (PID #####): Wrote XX rather than YY bytes of data to GATEWAY CONNECTED socket NNNNN.
Explanation: The Surrogate handler routine encountered an error trying to write data to the socket connected to the Library Management Gateway servlet (GATEWAY CONNECTED socket). The write() system call could not write the expected number of bytes to the socket. This may be due to the sockets' premature closing. IPC Surrogate terminates.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The XX is the number of bytes returned by the write() system call.
The YY is the number of bytes the Surrogate program attempted to write to the socket.
The NNNNN is the socket number to which the Surrogate was trying to write.
User Response:
Look for associated error message preceding this one that may indicate the cause.
Look for other associated errors on the Gateway, Adapter, and client machines.
Try to identify the ACSLS command that was being sent from the originating client system.
If possible, re-send the offending command with tracing turned on for the Surrogate, Gateway, and Adapter.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
surr_handler (PID #####): Unable to create a GATEWAY CONNECTED socket via ACCEPT (SURROGATE LISTENER NNNNN).
Explanation: The Surrogate handler routine was unable to complete an accept() system call on the main listener socket that it uses to accept requests from a Gateway servlet. Each Surrogate has a unique port number on which it is trying to listen(). A new socket connection for the Gateway servlet is created as a result of a successful accept() call known as a GATEWAY CONNECTED socket. IPC Surrogate terminates.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the port number on which the Surrogate is trying to listen.
User Response: This could be a possible hardware or network failure.
Look for associated errors that may indicate why the accept() call failed.
Kill the ACSLS system using the kill.acsss command.
Next, kill any additional ”zombie” ACSLS processes (using a ps | grep acs) and kill -9 appropriate IDs.
See if the socket is in use (possibly by another process) with a netstat -a | grep NNNNN where NNNNN is the socket number shown in the error message.
If the socket is in use, wait for a few minutes to see if the socket eventually times out. Then restart ACSLS with the rc.acsss command. It may be necessary to reboot the ACSLS host to release any hung sockets.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
surr_read_socket (PID #####): Read failed on GATEWAY CONNECTED socket NNNNN
Explanation: The Surrogate read socket routine was unable to complete an read() system call on the socket that it uses to accept requests from a Library Management Gateway servlet. Each Surrogate has a unique port number to which it is trying to listen(). A new socket connection for the Gateway servlet is created as a result of a successful accept() call known as a GATEWAY CONNECTED socket. The GATEWAY CONNECTED socket is closed and the IPC Surrogate continues running.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the port number from which the Surrogate is trying to read.
User Response:
Look for associated errors that may indicate why the read() call failed.
Kill the ACSLS system using the kill.acsss command.
Next, kill any additional ”zombie” ACSLS processes (using a ps | grep acs) and kill -9 appropriate IDs.
See if the socket is in use (possibly by another process) with a netstat -a | grep NNNNN where NNNNN is the socket number shown in the error message.
If the socket is in use, wait for a few minutes to see if the socket eventually times out. Then restart ACSLS with the rc.acsss command. It may be necessary to reboot the ACSLS host to release any hung sockets. This may be a result of a timeout of the command and increasing network timeout parameters may alleviate the condition.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
surr_read_socket (PID #####): Read X bytes from GATEWAY CONNECTED socket (NNNNN) but expected Y
Explanation: The Surrogate read socket routine was unable to complete an read() system call on the socket that it uses to accept requests from a Library Management Gateway servlet. Each Surrogate has a unique port number to which it is trying to listen(). A new socket connection for the Gateway servlet is created as a result of a successful accept() call known as a GATEWAY CONNECTED socket. It was trying to read Y number of bytes but only read X number of bytes. Surrogate continues running.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the port number from which the Surrogate is trying to read.
The X is the number of bytes that were successfully read.
The Y is the number of bytes that it was trying to read.
User Response:
Look for associated errors that may indicate why the read() call failed.
Kill the ACSLS system using the kill.acsss command.
Next, kill any additional ”zombie” ACSLS processes (using a ps | grep acs) and kill -9 appropriate IDs.
See if the socket is in use (possibly by another process) with a netstat -a | grep NNNNN where NNNNN is the socket number shown in the error message.
If the socket is in use, wait for a few minutes to see if the socket eventually times out. Then restart ACSLS with the rc.acsss command. It may be necessary to reboot the ACSLS host to release any hung sockets. This may be a result of a timeout of the command and increasing network timeout parameters may alleviate the condition.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
surr_read_socket (PID #####): select() call failed GATEWAY CONNECTED socket (NNNNN)
Explanation: The Surrogate handler routine failed on a select() system call. This routine blocks on the socket that it uses to accept requests from a Library Management Gateway servlet and on the socket it uses to communicate with the acslm process. Each Surrogate has a unique port number on which it is trying to listen(). A new socket connection for the Library Management Gateway servlet is created as a result of a successful accept() call known as a GATEWAY CONNECTED socket. IPC Surrogate terminates.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NNNNN is the port number for the Surrogate connected to the Surrogate.
User Response:
Look for associated errors that may indicate why the select() call failed.
See if the acslm process failed.
Check for the Gateway port using netstat -a | grep NNNNN.
Kill the ACSLS system using the kill.acsss command.
Kill any additional ”zombie” ACSLS processes (using a ps | grep acs) and kill -9 appropriate IDs.
See if the socket is in use (possibly by another process) with a netstat -a | grep NNNNN where NNNNN is the socket number shown in the error message.
If the socket is in use, wait for a few minutes to see if the socket eventually times out. Then restart ACSLS with the rc.acsss command. It may be necessary to reboot the ACSLS host to release any hung sockets.
Look for exceeding UNIX system limits on sockets, file descriptors, or other network resources.
If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
surr_handler (PID #####): COMMAND (ACK | INTERMEDIATE | FINAL) response discarded because original socket connection is no longer on the queue. Advise increasing SURROGATE_QUEUE_AGE.
Explanation: The ACSLS library manager returned a response to the Surrogate handler routine for the COMMAND shown, but the Surrogate could not find the outstanding request and socket connection on its queue, so its only alternative was to report the problem and discard (ignore) the response from the library manager. This may result from the library's taking too long to execute commands. For example, a mount or dismount may be taking an exceedingly long time because of hardware errors, a drive being cleaned before mounting, cartridges too far from the requested drive (such as different LSM), or other conditions. After a few minutes have passed (SURROGATE_QUEUE_AGE), the request on the queue is considered stale and removed from the queue. Eventually, when the library finally mounts or dismounts the tape, the FINAL response packet from the library manager can no longer be found on the queue and transmitted to the client. The Surrogate continues running.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The COMMAND is the ACS command for which the Surrogate could not find an outstanding request and socket connection.
The SURROGATE_QUEUE_AGE is the dynamic environment variable that controls how long the Surrogate keeps requests on its queue.
User Response:
Look for any unusual conditions that may cause ACS commands to be delayed (see the explanation above).
Determine if the hardware is malfunctioning or not configured correctly.
To increase the amount of time that the Surrogate keeps requests on its queue, increase the SURROGATE_QUEUE_AGE dynamic environment variable with the acsss_config program.
Restart the Surrogate to enable the change to take effect.
surr_query_server (PID #####): Surrogate process unable to issue query server (NN seconds)
Explanation: The Surrogate issues a query server request to the library manager when it starts running to be sure the library manager is ready to receive requests and before the Surrogate begins accepting requests from the Library Management Gateway socket. The Surrogate is expecting the server to be in RUN or RECOVERY mode. After waiting the number of seconds shown, the Surrogate determined that the query server could not be completed and gave up. The Surrogate abnormally terminates and is automatically restarted (up to 10 times) by the acsss_daemon.
Variable:
The ##### is the Process ID of the Surrogate issuing the error.
The NN is the number of seconds.
User Response:
Look for errors in the acsss_event.log that may explain why a query server request cannot be completed.
Try the query server request in cmd_proc.
surr_query_server (PID #####): Surrogate waiting for ACSLS to come up
Explanation: The Surrogate issues a query server request to the library manager when it starts running to be sure the library manager is ready to receive requests and before the Surrogate opens the Library Management Gateway listening socket to begin accepting requests. The Surrogate is expecting the server to be in RUN or RECOVERY mode. The Surrogate issues this message every 30 seconds (for up to 10 minutes) till a query server returns that it is in RUN or RECOVERY mode. Once it is in RUN or RECOVERY mode, the Surrogate continues coming up. If 10 minutes passes, then the surrogate abnormally terminates with error 2353. This can occur if the system starts up in IDLE mode.
Variable: The ##### is the Process ID of the Surrogate issuing the error.
User Response:
Look for errors in the acsss_event.log that may explain why a query server isn't in RUN or RECOVERY mode.
Try the query server request in cmd_proc.
Check to see if ACSLS is set to automatically start in IDLE mode using the acsss_config program.
If the system is in IDLE mode, issue a START command.
ss_main: Too many SURROGATE processes specified through acsss_config. The maximum is 10 SURROGATE_Processes.
Explanation: The acsss_daemon read the SURROGATE_PROCESSES dynamic environment variable in order to know how many surrogate processes to start. The number exceeds ten (10), the maximum allowed. ACSLS terminates.
Variable: The SURROGATE_PROCESSES is the dynamic environment variable that controls the number of surrogate processes running.
User Response: The range for the dynamic environment variable SURROGATE_PROCESSES has been set greater than the Surrogate program currently supports. Define the SURROGATE_PROCESSES variable with the acsss_config program to be a number less than 10.
surr_handler (PID #####): NN surrogate requests (open socket) being processed; cannot accept more until some finish. Advise reducing SURROGATE_QUEUE_AGE.
Explanation: The surrogate handler routine was unable to complete an accept() system call on the main listener socket that it uses to accept requests from a Library Management Gateway servlet. Each SURROGATE has a unique port number to which it is trying to listen(). A successful accept() call (known as a GATEWAY CONNECTED socket) creates a new socket connection for the Gateway servlet. The error code (errno) and message returned by the accept() system call is 24 - TOO MANY OPEN FILES.
The SURROGATE will disregard the Library Management Gateway's attempt to connect its servlet to a SURROGATE socket. As requests are completed and open socket connections are closed, future attempts to connect completes successfully. The SURROGATE does not abort on this error. Since it is possible for the Library Management Gateway to continue connection attempts (and fill the acsss_event.log), this error message will be displayed in the acsss_event.log no more often than every five (5) minutes. The SURROGATE continues running.
Variable:
The ##### is the process ID of the SURROGATE issuing the error.
The NN is the number of open sockets.
The SURROGATE_QUEUE_AGE is the dynamic environment variable that controls the length of time a request remains in the queue.
User Response: Generally the problem is that the Library Management Gateway has sent more requests than the ACSLS system can process (or has sent them too fast) or that the ACSLS library system is processing the requests too slowly. Thus, the SURROGATE has reached the maximum limit of open files (sockets).
Look for errors in the acsss_event.log that may show indicate hardware or configuration errors.
Try a query request all command in cmd_proc to see how many requests ACSLS are outstanding.
Check client software to see if many mount and dismount requests are being sent.
It may also be necessary to reduce the amount of time that the SURROGATE keeps outstanding requests on its queue. Reduce the SURROGATE_QUEUE_AGE dynamic environment variable with the acsss_config program.
Restart the SURROGATE so that the change takes effect.
Volume vol_id: Media type incompatible with L5500. Not entered.
Explanation: This message pertains to L5500 LSMs only; it indicates an attempt to enter an incompatible cartridge into an L5500 CAP. Only LTO and 9840/9940 cartridges are compatible with L5500 LSMs. Requests to enter incompatible media are rejected.
Variable: The vol_id is the volume entered into the CAP.
User Response: Remove the cartridge from the CAP. Substitute an LTO or 9840/9940 cartridge.
Cell cell_id contains incompatible media: must be manually removed.
Explanation: This message pertains to L5500 LSMs only. The message indicates that an audit found a cartridge that is neither an LTO cartridge nor a StorageTek 9840 or 9940 cartridge in an L5500 panel. Only LTO and 9840/9940 cartridges are compatible with L5500 LSMs. (This may have been caused by someone physically entering the LSM and manually placing the cartridge in the panel.)
Variable: The cell_id is the cell in the L5500 containing the incompatible cartridge.
User Response: Manually enter the L5500 and manually remove the incompatible cartridge.
Dropping remaining responses for command command, request sequence number request_seq_nbr from client client_IP_address because unable to return intermediate responses.
Explanation: An ACSAPI client made a request that causes ACSLS to return multiple responses. The ACSLS CSI was unable to return one of the response to the client application because of network problems or because the client did not receive the response. A partial set of responses to this request would be incomplete, so the CSI will drop all remaining responses to the request. This avoids clogging the CSI with attempts to re-send the remaining responses to an unresponsive client.
This message is followed by a 2366 or 2367 message with the same request_seq_nbr when all the responses for the request have been processed.
Any new requests from the client are processed and responses are returned to the client. Only the responses to the specified request are dropped.
Variable:
The command is the request that was dropped, such as MOUNT or QUERY.
The request_seq_nbr is the request sequence number that was assigned by the SSI on the client system to identify the request.
The client_IP_address is the IP address of the client system that sent the request.
User Response: None for the ACSLS server. The CSI continues to process new requests from all client applications.
Determine why the client at the IP address specified was unable to receive responses.The client's server could have rebooted, the client's SSI could have terminated, or there could have been network problems. If any problems with the client application or network have been resolved, no further action is needed. ACSLS continues to process new requests from the client.
Dropping remaining responses for command command, request sequence number request_seq_nbr from client client_IP_address. First response failed at time_response_failed, and unable to return response_count responses since.
Explanation: An ACSAPI client made an audit, enter, eject, or event notification request that causes ACSLS to return multiple responses. The ACSLS CSI was unable to return one of the responses to the client application because of network problems or because the client did not receive the response. The ACSLS CSI continued to try to return responses but exceeded the maximum number of attempts to resend responses.The CSI drops all remaining responses to the request. This avoids clogging the CSI with attempts to re-send the remaining responses to an unresponsive client.
This message is followed by a 2366 or 2367 message with the same request_seq_nbr when all the responses for the request have been processed.
Any new requests from the client are processed with responses returned to the client. Only the responses to the specified request are dropped.
Variable:
The command is the request that was dropped, such as AUDIT or REGISTER.
The request_seq_nbr is the request sequence number that was assigned by the SSI on the client system to identify the request.
The client_IP_address is the IP address of the client system that sent the request.
The time_response_failed is the first time that an attempt to send a response failed.
The response_count is the total number of responses that ACSLS could not return to the client before dropping the remaining responses.
User Response: None for the ACSLS server. The CSI continues to process new requests from all client applications.
Determine why the client at the IP address specified was unable to receive responses. The client's server could have rebooted, the client's SSI could have terminated, or there could have been network problems.
If any problems with the client application or network have been resolved, no further action is needed. ACSLS continues to process new requests from the client.
Unable to return response_count responses for command command, request sequence number request_seq_nbr from client client_IP_address. First response failed at time_response_failed
Explanation: An ACSAPI client sent a request that causes ACSLS to return multiple responses. The ACSLS CSI was unable to return one or more of the responses to the client application because of network problems or because the client did not receive the response. The ACSLS CSI eventually dropped the remaining responses to the request to avoid clogging the CSI with attempts to resend the remaining responses to an unresponsive client.
A message 2364 or 2365 was reported when the CSI started dropping responses to the request. This message is displayed after the final response to the request was processed and gives the total number of responses dropped. You can find the earlier message by the request_seq_nbr.
Any new requests from the client are processed with responses returned to the client. Only the responses to the specified request are dropped.
Variable:
The response_count is the total number of responses that ACSLS could not return to the client.
The command is the request that was dropped, such as DISPLAY or QUERY.
The request_seq_nbr is the request sequence number that was assigned by the SSI on the client system to identify the request.
The client_IP_address is the IP address of the client system that sent the request.
The time_response_failed is the first time that an attempt to send a response failed.
User Response: None for the ACSLS server. The CSI continues to process new requests from all client applications.
Determine why the client at the IP address specified was unable to receive responses. The client's server could have rebooted, the client's SSI could have terminated, or there could have been network problems.
If any problems with the client application or network have been resolved, no further action is needed. ACSLS continues to process new requests from the client.
Unable to return response_count responses for command command, request sequence number request_seq_nbr from client client_IP_address. First response failed at time_response_failed. Final response never received and entry aged off queue.
Explanation: An ACSAPI client sent a request that causes ACSLS to return multiple responses. The ACSLS CSI was unable to return one or more of the responses to the client application because of network problems or because the client did not receive the response.The ACSLS CSI eventually dropped the remaining responses to the request to avoid clogging the CSI with attempts to resend the remaining responses to an unresponsive client.
A message 2364 or 2365 was reported when the CSI started dropping responses to the request. This message is displayed because the final response to the request was never passed to the CSI. It gives the total number of responses dropped. You can find the earlier message by the request_seq_nbr.
Any new requests from the client are processed with responses returned to the client. Only the responses to the specified request are dropped.
Variable:
The response_count is the total number of responses that ACSLS could not return to the client.
The command is the request that was dropped, such as AUDIT or QUERY.
The request_seq_nbr is the request sequence number that was assigned by the SSI on the client system to identify the request.
The client_IP_address is the IP address of the client system that sent the request.
The time_response_failed is the first time that an attempt to send a response failed.
User Response: None for the ACSLS server. The CSI continues to process new requests from all client applications.
Determine why the client at the IP address specified was unable to receive responses. The client's server could have rebooted, the client's SSI could have terminated, or there could have been network problems.
If any problems with the client application or network have been resolved, no further action is needed. ACSLS continues to process new requests from the client.
ACS: acs_id; LMU error: Co_4400:st_parse_error: Request: request_type Error: error_code - error_explanation
Explanation: When an ACSLS request that does not involve cartridge movement request fails, this message both describes the original request and explains why it failed. This message only reports on failing requests in HLI-attached libraries, such as SL8500s, SL3000s, and 9310s. To avoid filling up the Event Log with requests that may fail frequently, the following failures are not reported in this message:
0310 - cannot cancel enter on release requests
0416 - request cancelled (when a request in progress is cancelled)
Variable:
The acs_id is the ACS where the error occurred
The request_type is the type of non-movement request
The error_code is an internal four-digit error code (a two digit error category followed by a two digit error code).
The error_explanation explains the error.
User Response: ACSLS may automatically recover from the failed request, or the failure may be returned to the client application. This message helps you understand what happened and how to address any problems. The ACSLS component that requested the library action may issue related messages following this message when it receives the failure response.
Example:
In the Catalog (audit) failure below:
ACS:1
Request Attempted: Catalog Cell - Catalog is the request that is sent to the library to examine a specific location(s) (a cell, a drive, or a CAP cell).
2012-05-03 21:43:35 ACSLH[0]: 2377 N Co_ProcessResponses.C 1 609 ACS: 1; LMU error: Co_4400:st_parse_error: Request: Catalog Cell Error: 0401 - General procedure error: LSM is not ready
ACS: acs_id; LMU error: Co_4400:st_parse_error: Error: error_code - error_explanation Request: request_type volser; vol_id, media domain: media_domain, media_type: media_type source: source_type source_location destination:destination_type destination_location stuck in location: stuck_location.
Explanation: When an ACSLS cartridge movement request fails, this message both describes the original request and explains why it failed. ACSLS cartridge movement requests include mounts, dismounts, moves, enters, and ejects. This message only reports on failing movement requests in HLI-attached libraries, such as SL8500s, SL3000s, and 9310s. To avoid filling up the Event Log with requests that may fail frequently, the following failures are not reported in this message:
0416 - request cancelled (when a request in progress is cancelled)
0424 - drive is empty (on a dismount)
0426 - drive is not rewound (Returned on a dismount. To dismount the cartridge, specify the force option.)
Variable:
The acs_id is the ACS where the error occurred.
The error_code is an internal four-digit error code (a two digit error category followed by a two digit error code).
The error_explanation explains the error.
The request_type is the type of movement request (mount, dismount, move, enter, or eject).
The vol_id is the volume ID of the cartridge being moved.
The media_domain is the media domain of the cartridge (such as T for T10000 data or L for LTO data cartridges).
The media_type is the media type of the cartridge (such as 1 for T10000 data or 4 for LTO Gen 4 data cartridges).
The source_type is the starting location for the move. The source type can be a cell, drive, or cap.
The source_location is the source location for the move. Source locations can be: cell (acs,lsm,panel,row,column); drive (acs,lsm,panel,drive); or CAP cell (acs,lsm,cap,row,column).
The destination_type is the ending location for the move. The destination type can be a cell, drive, or cap.
The destination_location is the destination location for the move. Destination locations can be: cell (acs,lsm,panel,row,column); drive (acs,lsm,panel,drive); drive w write protect (acs,lsm,panel,drive); CAP cell (acs,lsm,cap,row,column).
In the stuck_location if the cartridge was not returned to the source after the failed move, the stuck in location: line is present. Normally the library is able to return a cartridge to the source location. These stuck in locations may be displayed: LSM (acs,lsm) Hand hand_nbr; LSM(acs,lsm) PTP Panel panel_nbr; or drive (acs,lsm,panel,drive).
User Response: ACSLS may automatically recover from the failed movement request, or the failure may be returned to the client application. This message helps you understand what happened and how to address any problems. The ACSLS component that requested the cartridge movement may issue related messages following this message when it receives the failure response.
Example: In the cartridge movement failure below:
ACS: 0
Error: On a dismount (next line), unable to unload the drive.
Movement attempted: dismount, force (force means that a rewind and unload command was sent to the drive).
Cartridge involved (LA9922), the media domain and type
Source location (start of the attempted movement) - drive 0,0,1,8.
Destination of the attempted move - cell 0,0,2,30,0
Cartridge remains stuck in the drive (because the drive could not unload the cartridge).
2378 N Co_ProcessResponses.C 1 1389
ACS: 0; LMU error: Co_4400:st_parse_error:
Error: 0977 - LSM logical error: Unable to unload drive
Request: Dismount, forced rewind and unload
Volser: LA9922, media domain: 0, media type: P
Source: Drive 0,0,1,8
Destination: Cell 0,0,2,30,0
Stuck in location: Drive 0,0,1,8
Error di_status on SQL select * from logical_acs_table where logical_acs = logical_acs_id.
Explanation: An attempt to read the specified logical_acs failed with an unexpected error code.
Variable:
The di_status is the Database Interface error status returned from the SQL select on the logical_acs_table.
The logical_acs_id is the logical_acs on which the SQL select failed.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error di_status on SQL select * from logical_drive_table where physical drive = drive_id.
Explanation: An attempt to read the logical_drive associated with the specified physical drive failed with an unexpected error code.
Variable:
The di_status is the Database Interface error status returned from the SQL select on the logical_acs_table.
The drive_id is the physical drive ID associated with the logical_drive on which the SQL select failed.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Error di_status on SQL select * from logical_drive_table where vol_id = vol_id.
Explanation: An attempt to read the specified logical volume failed with an unexpected error code.
Variable:
The di_status is the Database Interface error status returned from the SQL select on the logical_acs_table.
The vol_id is the volume ID on which the SQL select failed.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Unexpected di_status: di_status received on update of logical_volume_table for volume vol_id
Explanation: An attempt to update the specified logical volume failed with an unexpected error code.
Variable:
The di_status is the Database Interface error status returned from the SQL select on the logical_acs_table.
The vol_id is the volume ID on which the SQL select failed.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL Lock timeout on update of logical_volume_table * where volid = vol_id
Explanation: An attempt to update the specified logical volume failed with a timeout on an attempt to get a lock on the database record.
Variable: The vol_id is the volume ID on which the SQL update failed.
User Response: Retry the operation. The lock on the database record should now be released.
Error di_status on SQL update of logical_volume_table where vol_id = vol_id.
Explanation: An attempt to update the specified logical volume failed with an unexpected error code.
Variable:
The di_status is the Database Interface error status returned from the SQL select on the logical_acs_table.
The vol_id is the volume ID on which the SQL select failed.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
No unassigned home cell locations in logical library logical_acs_id.
Explanation: There are no unassigned home addresses for this logical library. Additional volumes cannot be assigned to the logical library until the capacity is increased or other logical volumes are unassigned or ejected. If volumes that are assigned to the logical library and were ejected are re-entered into the physical ACS, they are not available until the capacity is increased or other logical volumes are ejected or unassigned.
Variable: The logical_acs_id is the logical_acs which has no unassigned home cell locations.
User Response: You can increase the capacity of a logical library by editing the logical library and increasing the cell capacity of the logical library. You can free up logical volume home addresses by ejecting logical volumes from the logical and/or physical library, or by un-assigning volumes from the logical library.
SQL select generate series for unassigned home address in logical_volume_table for logical library logical_acs_id, failed with di_status = di_status
Explanation: An attempt to determine the unassigned home addresses for logical volumes in the specified logical library failed with an unexpected error code.
Variable:
The logical_acs_id is the logical_acs on which the attempt to determine the unassigned home addresses failed.
The di_status is the Database Interface error status returned from the SQL statement.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL select failed on table table_name.
Explanation: An ODBC call to prepare an SQL statement for selecting records from table table_name has failed.
Variable: The table_name is the name of the table from which the records were to be selected.
User Response: Restart the application server. If the problem persists, restart the database. If the problem continues, contact your System Administrator.
XML Error (error_message) with error code (code).
Explanation: An XML Exception has occurred.
Variable:
The error_message is the XML Exception message
The code is the error code from the XML Exception.
User Response: Check the validity of the XML in the Request.
XML Parsing Error (error_message).
Explanation: A SAX Exception has occurred in parsing the XML.
Variable: The error_message is the SAX Exception message.
User Response: Check the validity of the XML in the Request.
Invalid DISPLAY type detected.
Explanation: The type in the display response packet is invalid.
Variable: None.
User Response: Retain the request XML and the response from the display processor. If the problem persists, contact Oracle Support.
Display tables could not be loaded.
Explanation: The display reference tables could not be loaded into the database during configuration.
Variable: None.
User Response: Restart the database. If the problem persists, contact your System Administrator.
EXEC SQL Cannot create database handle.
Explanation: An ODBC call to specify the variables to store the records from the database has failed.
Variable: None.
User Response: Restart the application server. If the problem persists, restart the database. If the problem continues, contact your System Administrator.
EXEC SQL Cannot register variables
Explanation: An ODBC call to specify the variables to store the records from the database has failed.
Variable: None.
User Response:
Restart the application server.
If the problem persists, restart the database.
If the problem continues, contact your System Administrator.
Unexpected XML parsing error occurred.
Explanation: An unexpected parsing error occurred in the XML4c APIs.
Variable: None.
User Response: Restart the application server. If the problem continues, contact your System Administrator. If the problem continues, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
acsdisp failed, database query string too long.
Explanation: The database query is too long to be passed through ODBC to query the database.
Variable: None.
User Response: Please enter a shorter query.
Error while loading Module module_name.
Explanation: You tried to run the install_scsi_Linux.sh script when the device is in use.
Variable: The module_name is the name of the module.
User Response:
Wait for all device operations to complete.
Idle the ACSLS server from cmd_proc.
Kill the ACSLS server using kill.acsss.
Run install_scsi_Linux.sh.
Module module_name successfully loaded.
Explanation: The module has been loaded and is ready to attach devices.
Variable: The module_name is the name of the module.
User Response: None.
No SCSI medium changers are attached.
Explanation: The possible reasons for this are:
No SCSI devices are attached to the server.
The SCSI devices are attached and the module is loaded, but it does not detect any medium changer devices.
Variable: None.
User Response: If you want to attach SCSI medium changers:
Power off the server.
Attach the SCSI medium changers, then boot up the server.
Run install_scsi_Linux.sh script.
Could not generate major number for SCSI device.
Explanation: GNU/Linux has a limitation of 256 major numbers (from 0-255). All of them are already used by the other device drivers.
Variable: None.
User Response: Remove the unwanted device driver modules using rmmod. Run install_scsi_Linux.sh.
Node node_name assigned for Model-model_name Channel-channel_num Id-id_num.
Explanation: This informational message describes how the hardware is mapped to the GNU/Linux OS file system. It displays the node-name that has been assigned on the file system for the SCSI medium changer which is attached to the server at the specified channel_num and id_num. You can use this information to configure the SCSI libraries through acsss_config.
Variable:
The node_name is the name of the node on the file system.
The model_name is the name of the SCSI device model attached to the server.
The channel_num identifies the channel connected to the SCSI bus.
The id_num represents the identifier allocated to the SCSI device.
User Response: None.
Failed to create the node_name.
Explanation: The script failed to create the special file for the SCSI device.
Variable: The module_name is the name of the module.
User Response:
Remove the unwanted nodes using rm.
Run install_scsi_Linux.sh
Failed to remove the Module module_name.
Explanation: The script tried to remove the module when the device was in use.
Variable: The module_name is the name of the module.
User Response:
Wait for all device operations to complete.
Idle the ACSLS server from cmd_proc.
Kill the ACSLS server using kill.acsss.
Run install_scsi_Linux.sh.
Device information file module_info_file not found.
Explanation: The module_info_file was not found or was deleted while loading the module.
Variable: The module_info_file is the name of the file that contains information about the SCSI devices connected to the server.
User Response:
Re-run install_scsi_Linux.sh.
Reboot the server.
EXEC SQL failed to fetch from cursor.
Explanation: An ODBC call to prepare an SQL statement for fetching a row from the database with the cursor has failed.
Variable: The cursor is the database handle for executing SQL statement.
User Response: The application server has to be re-started. Contact your System Administrator.
DB status [err_num] detected on update for client id client_id.
Explanation: An attempt to update a client record in the database failed.
Variable:
The err_num is the error number.
The client_id is the identifier of the client to be updated.
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
DB status [err_num] detected on insert for client id clnt_id.
Explanation: An attempt to insert a client record into the database has failed.
Variable:
The err_num is the error number.
The clnt_id is the identifier of the client to be inserted.
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support
EXEC SQL failed to insert client_id clnt_id into clienttable.
Explanation: An ODBC call to prepare an SQL statement for inserting a client record into the database has failed.
Variable: The clnt_id is the identifier of the client to be inserted.
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL lock timeout on update of clienttable where client_id = clnt_id
Explanation: An attempt to update a locked client record from clienttable has failed.
Variable: The clnt_id is the identifier of the client to be updated.
User Response:
If it does, restart the database and see if the problem persists.
Restart the application server and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL failed to update clienttable where client_id = clnt_id
Explanation: An ODBC call to prepare an SQL statement for updating a client record has failed.
Variable: The clnt_id is the identifier of the client to be updated.
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
DB status [err_num] detected on operation for lib_cmpnt cmpnt_id
Explanation: An attempt to perform a database operation like the insertion, deletion or updating of a library component lib_cmpnt, such as LMU or PTP or HAND or PANEL with an identifier cmpnt_id, such as 0,0(lmu_id) or 0,0,0 (panel_id or ptp_id) or 0,0,0,0 (hand_id), has failed.
Variable:
The err_num is the error number.
The lib_cmpnt is the library component type, such as LMU, PTP, HAND or PANEL.
The cmpnt_id is the identifier of a library component, such as 0,0(lmu_id) or 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id).
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL lock timeout on delete from table_name where lib_cmpnt = cmpnt_id
Explanation: An attempt to delete a locked record from the table_name, such as lmutable, ptptable or handtable for a library component lib_cmpnt; LMU, PTP or HAND with an identifier cmpnt_id, such as 0,0(lmu_id) or 0,0,0(ptp_id) or 0,0,0,0(hand_id), has failed.
Variable:
The table_name is the name of the database table from which row has to be deleted.
The lib_cmpnt is the library component type, such as LMU, PTP or HAND.
The cmpnt_id is the identifier of the library component, such as 0,0(lmu_id) or 0,0,0(ptp_id) or 0,0,0,0(hand_id).
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
EXEC SQL delete from table_name failed, where lib_cmpnt = cmpnt_id
Explanation: An ODBC call to prepare an SQL statement for deleting a record from the table_name, such as lmutable, ptptable or handtable for a library component, like that of the following: LMU, PTP or HAND with an identifier cmpnt_id, such as 0,0(lmu_id) or 0,0,0(ptp_id) or 0,0,0,0(hand_id), has failed.
Variable:
The table_name is the name of the database table from which row has to be deleted.
The lib_cmpnt is the library component type, such as LMU, PTP or HAND.
The cmpnt_name is the name of the database table from which row has to be deleted.
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support..
EXEC SQL select from table_name failed, where lib_cmpnt = cmpnt_id
Explanation: An ODBC call to prepare an SQL statement for selecting a record from the table_name, such as lmutable, ptptable or handtable for a library component LMU, PTP or HAND with an identifier cmpnt_id, such as 0,0(lmu_id) or 0,0,0(ptp_id) or 0,0,0,0(hand_id), has failed.
Variable: The table_name is the name of the Access Control temporary database table.
The options are:
The clientinfo.temp: This maps IP addresses to client user_names. It is loaded from the internet.addresses file.
The lib_cmpnt is a library component type, such as LMU, PTP or HAND.
The cmpnt_id is the identifier of a library component 0,0(lmu_id), 0,0,0(ptp_id) or 0,0,0,0(hand_id).
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
Table table_name loading failed.
Explanation: ACSLS loads Access Control data files to temporary database tables before rebuilding the Access Control database tables. An attempt to load an Access Control data file to the specified temporary Access Control database table failed.
Variable: The table_name is the name of the Access Control temporary database table.
The options are:
The clientinfo.temp: This maps IP addresses to client user_names. It is loaded from the internet.addresses file.
The cmdaccess.temp: For Command Access Control, this grants users access to commands. It is loaded from the command.COMMAND.allow and command.COMMAND.disallow files.
The volaccess.temp: For Volume Access Control, this controls access to one user's volumes by other users. It is loaded from the users.COMMAND.allow files.
The volownership.temp: This defines policies for setting volume ownership. It is loaded from the ownership.assignments file.
User Response:
If ACSLS is running, execute acsss_config as user acsss and select the option to rebuild the Access Control tables.
If ACSLS is not running, execute acsss enable as user acsss.
If the problem persists, there is probably a duplicate key for the Access Control table that you are trying to load. The duplicate keys are always composite keys of two fields. To find the duplicate key:
Look at /tmp/ac_err.log for messages identifying the specific load failure.
Find the duplicate key in the affected files.
•The clientinfo.temp: The composite key consists of the IP address and user name (ID) in the internet.addresses file. Duplicate IP addresses and client names should have been identified while processing the internet_addresses file in preparation for loading it to the database.
•The clientinfo.temp: The composite key consists of the IP address and user name (ID) in the internet.addresses file. Duplicate IP addresses and client names should have been identified while processing the internet_addresses file in preparation for loading it to the database.
•The cmdaccess.temp: The composite key consists of the command name and the user ID from each line in the command.ALL.allow and command.ALL.disallow, as well as command.COMMAND.allow and command.COMMAND.disallow files
Note:
Allow and disallow is an attribute, and not a part of the key. The same command+user combination in both an allow and a disallow file causes a duplicate key.•The volaccess.temp: The composite key consists of the owner ID and each user ID from the users.ALL.allow & users.ALL.allow and users.COMMAND.allow & users.COMMAND.disallow files.
Note:
Allow and disallow is an attribute, and not a part of the key. The same owner+user combination in both an allow and a disallow file causes a duplicate key. A duplicate key is also caused when the same user is specified twice for an owner.•The volownership.temp: A line may have been repeated in the ownership.assignments file. Problems should have been caught while processing the file in preparation for loading it to the database.
If you are unable to identify the duplicate key, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Contact Oracle Support.
You can temporarily disable Access Control by setting AC_CMD_ACCESS and AC_VOL_ACCESS to FALSE using acsss_config. This will let you enable ACSLS while you are diagnosing the problem.
Table table_name rebuilding failed.
Explanation: To ensure that the Access Control database tables are locked while they are rebuilt, ACSLS loads Access Control data files to temporary database tables and uses the temporary tables to rebuild the Access Control database tables. This message indicates that an attempt to rebuild a specified Access Control database table has failed.
Variable: The table_name is the name of the Access Control database table that ACSLS failed to rebuild.
User Response:
If ACSLS is running, execute acsss_config as user acsss and select the option to rebuild the Access Control tables.
If the problem persists, see the information for message 2430 for details about how to resolve the problem.
If you are still unable to resolve the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Access Control tables have been rebuilt.
Explanation: ACSLS has successfully rebuilt the Access Control tables.
Variable: None.
User Response: None.
EXEC SQL lock timeout: on insert into table_name, where identifier = id.
Explanation: An attempt to insert a record into the locked table table_name, such as clienttable, lmutable, ptptable, paneltable or handtable, where identifier identifier, such as client_id, lmu_id, ptp_id, panel_id or hand_id (with a value of id), such as of client1 (client_id) or 0,0(lmu_id) or 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id), has failed.
Variable:
The table_name is the name of the database table for which a row should be inserted.
The identifier is an identifier, like that of the following: client_id, lmu_id, ptp_id, panel_id or hand_id.
The id is the value of an identifier, like that of the following: client1(client_id), 0,0(lmu_id) or 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id).
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
If it does, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
EXEC SQL failed lock to insert into table_name, where identifier = id.
Explanation: An ODBC call to prepare an SQL statement to insert a record into table table_name, such as lmutable, ptptable, paneltable or handtable, where identifier identifier, such as lmu_id, ptp_id, panel_id or hand_id with a value of id, such as 0,0(lmu_id) or 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id), has failed.
Variable:
The table_name is the name of the database table from which row has to be deleted.
The identifier is an identifier, such as ptp_id, panel_id or hand_id.
The id is the value of an identifier, such as 0,0(lmu_id) or 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id).
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
If it does, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
EXEC SQL lock timeout: on update table_name, where identifier = id.
Explanation: An attempt to update a record in the database for a locked table table_name such as: Imutable, ptptable, paneltable or handtable, where identifier identifier, such as Imu_id, ptp_id, panel_id or hand_id, with a value of id, such as 0,0(lmu_id) or 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id) has failed.
Variable:
The table_name is the name of the database table from which row has to be deleted.
The identifier is an identifier, like that of the following: lmu_id, ptp_id, panel_id or hand_id.
The id is the value of an identifier, such as 0,0(lmu_id), 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id).
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
If it does, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
EXEC SQL update of table_name failed, where identifier = id.
Explanation: An ODBC call to prepare an SQL statement for updating a record in the database for the table table_name, such as lmutable, ptptable, paneltable or handtable, where identifier identifier lmu_id, ptp_id, panel_id or hand_id, with a value of id such as 0,0(lmu_id) or 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id) has failed.
Variable:
The table_name is the name of the database table from which a row has to be deleted.
The identifier is an identifier, such as lmu_id, ptp_id, panel_id or hand_id.
The id is the value of an identifier, such as 0,0(lmu_id) or 0,0,0(ptp_id or panel_id) or 0,0,0,0(hand_id).
User Response:
Restart the application server and see if the problem persists.
If it does, restart the database and see if the problem persists.
If it does, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
EXEC SQL fetch from handtable failed.
Explanation: An ODBC call to prepare an SQL statement for fetching a record from handtable has failed.
Variable: None.
User Response:
Restart the application to see if the problem persists.
If it does, restart the database.
If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support"). Then contact Oracle Support.
PTP ptp_id, configuration failed to verify
Explanation: ACSLS has discovered a mismatch between hardware and the database during recovery. PTP information needs to be added to or deleted from the database.
Variable: The PTP identifier is ptp_id.
User Response: After recovery processing terminates, rerun the library server acsss_config program to redefine the library configuration in the database (see the Administrator's Guide for your platform).
Hand hand_id, configuration failed to verify
Explanation: ACSLS has discovered a mismatch between hardware and the database during recovery. Hand information needs to be added to or deleted from the database.
Variable: The HAND identifier is hand_id.
User Response: After recovery processing terminates rerun the library server acsss_config program to redefine the library configuration in the database (see the Administrator's Guide for your platform).
lib_cmpnt cmpnt_id is operative.
Variable:
The lib_cmpnt is the library component type, such as PTP, HAND, DRIVE or CAP.
The cmpnt_id is the identifier of a library component, such as 0,0,0(ptp_id) or 0,0,0,0(hand_id) or 0,0,0(cap_id) or 0,0,7,1(drive_id).
User Response: None.
lib_cmpnt cmpnt_id is inoperative.
Explanation: This message is issued when the library component lib_cmpnt, such as PTP, HAND, DRIVE or CAP, with an identifier cmpnt_id 0,0,0(ptp_id), 0,0,0,0(hand_id), 0,0,0(cap_id) or 0,0,7,1(drive_id) becomes inoperative.
Variable:
The lib_cmpnt is the library component type, such as PTP, HAND, DRIVE or CAP.
The cmpnt_id is the identifier of a library component, like that of the following: 0,0,0(ptp_id), 0,0,0,0(hand_id), 0,0,0(cap_id) or 0,0,7,1(drive_id).
User Response: None.
CAP CAP_id: CAP closed.
Explanation: The CAP with value CAP_id was closed.
Variable: The CAP_id is the CAP that was closed.
User Response: None.
lib_cmpnt cmpnt_id serial number changed.
Explanation: This message indicates that there is a change in serial number for a library component, such as LSM or DRIVE, with an identifier cmpnt_id, such as 0,0(lsm_id) or 0,0,7,1(drive_id).
Variable:
The lib_cmpnt is the library component type, such as LSM or DRIVE.
The cmpnt_id is the identifier of a library component, such as 0,0(lsm_id) or 0,0,7,1(drive_id).
User Response: None.
Drive drive_id type changed.
Explanation: The type is changed for the DRIVE identifier with the value drive_id.
Variable: The drive_id is the value of the DRIVE identifier.
User Response: None.
LMU lmu_id type changed.
Explanation: The type is changed for the LMU identifier with the value lmu_id.
Variable: The lmu_id is the value of the LMU identifier.
User Response: None.
LSM lsm_id type changed.
Explanation: The type is changed for the LSM identifier with the value lsm_id.
Variable: The lsm_id is the value of LSM identifier
User Response: None.
lib_cmpnt cmpnt_id added.
Explanation: A library component, such as DRIVE, with an identifier cmpnt_id, such as 0,0,7,1(drive_id), has been added to the database.
Variable:
The lib_cmpnt is the library component type, such as DRIVE.
The cmpnt_id is the identifier of a library component, such as 0,0,7,1(drive_id).
User Response: None.
lib_cmpnt cmpnt_id removed.
Explanation: A library component, such as DRIVE, with an identifier cmpnt_id, such as 0,0,7,1(drive_id), has been removed.
Variable:
The lib_cmpnt is the library component type, such as DRIVE.
The cmpnt_id is the identifier of a library component, such as 0,0,7,1(drive_id).
User Response: None.
lib_cmpnt cmpnt_id maintenance required.
Explanation: A library component, such as LSM, with an identifier cmpnt_id, such as 0,0(lsm_id), is in maintenance mode.
Variable:
The lib_cmpnt is the library component type, such as LSM.
The cmpnt_id is the identifier of a library component, such as 0,0(lsm_id).
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Support.
lib_cmpnt cmpnt_id HLI Compatibility Level changed.
Explanation: The HLI compatibility level has changed for a library component, such as ACS or LMU with an identifier cmpnt_id, such as 0(acs_id) or 0,0(lmu_id).
Variable:
The lib_cmpnt is the library component type, such as ACS or LMU.
The cmpnt_id is the identifier of a library component, such as acs_id or lmu_id.
User Response: None.
LMU lmu_id is now standalone.
Explanation: The status of LMU with value lmu_id is that of a standalone LMU.
Variable: The lmu_id is the value of the LMU identifier.
User Response: None.
LMU lmu_id is now active.
Explanation: The status of LMU, with value lmu_id, is that of the active LMU.
Variable: The lmu_id is the value of LMU identifier.
User Response: None.
LMU lmu_id is now standby.
Explanation: The status of the LMU, with the value lmu_id, is that of the standby LMU.
Variable: The lmu_id is the value of LMU identifier.
User Response: None.
Server system configuration changed.
Explanation: This message is issued when the server system configuration is changed.
User Response: None.
Volume vol_id entered.
Explanation: This message is issued when VOLUME, with value vol_id, is entered into the library.
Variable: vol_id is the VOLUME identifier.
User Response: None.
Volume vol_id reactivated.
Explanation: This message is issued when VOLUME, with value vol_id that was absent, is reactivated.
Variable: The vol_id is the VOLUME identifier.
User Response: None.
Volume vol_id ejected.
Explanation: This message is issued when VOLUME, with value vol_id, is ejected from the library.
Variable: The vol_id is the VOLUME identifier.
User Response: None.
Volume vol_id absent.
Explanation: This message is issued when VOLUME, with value vol_id, is marked absent.
Variable: The vol_id is the VOLUME identifier.
User Response: None.
Cleaning cartridge vol_id usage limit exceeded.
Explanation: A cleaning cartridge, with the value vol_id, has exceeded its maximum usage limit.
Variable: The vol_id is the VOLUME identifier.
User Response: None.
Cleaning cartridge vol_id is spent.
Explanation: The cleaning capacity of the cleaning cartridge with the value vol_id is spent (used-up). The cleaning cartridges' usage will be updated above its maximum use and will be marked as a spent cleaning cartridge.
Variable: The vol_id is the identifier of the cleaning cartridge.
User Response: Eject the cleaning cartridge.
lib_cmpnt cmpnt_id reported a Unit Attention.
Explanation: An error was reported for a library component. This message is from the Event Notification component. See the preceding messages for details about the problem. The library component is still operational after a Unit Attention Status is reported, but it may be in a degraded mode.
Variable:
The lib_cmpnt is library component type, such as LSM, DRIVE or CAP.
The cmpnt_id is the identifier of a library component, such as lsm_id, cap_id or drive_id.
User Response: Review the specific status reported in earlier messages and respond to the problem reported. If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
lib_cmpnt cmpnt_id reported a hardware error.
Explanation: An LSM reported a Hardware Error. This message is from the Event Notification component. Look for a preceding message from ACSLH scsilh that reports the specific hardware error. The library is still operational after a hardware error is reported, but it may be in a degraded mode.
Variable:
The lib_cmpnt is library component type, such as LSM, DRIVE or CAP.
The cmpnt_id is the identifier of a library component, such as lsm_id, cap_id or drive_id.
User Response: Review the specific status reported earlier and respond to the problem reported. If this does not fix the problem, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
LSM lsm_id access door closed..
Explanation: The access door of the LSM with value lsm_id is closed.
Variable: The lsm_id is the value of LSM identifier.
User Response: None.
LSM lsm_id access door opened.
Explanation: The access door of the LSM, with value lsm_id, is open.
Variable: The lsm_id is the value of the LSM identifier.
User Response: None.
Failed to add lib_cmpnt cmpnt_id into the examine list.
Explanation: ACSLS discovered an internal error while examining a library component, such as LSM, CAP or DRIVE. To avoid recursive examinations, each component being examined is added to a list. This error is reported when a failure in memory allocation prevents the addition of a component to the list.
Variable:
The lib_cmpnt is the library component type, such as LSM, DRIVE or CAP.
The cmpnt_id is the identifier of a library component, such as lsm_id, cap_id or drive_id.
User Response:
Restart ACSLS - if the error continues to be reported, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Failed to delete lib_cmpnt cmpnt_id from the examine list.
Explanation: ACSLS discovered an internal error while examining library component, such as LSM, CAP or DRIVE. The component is deleted from the examination list when the exam is completed. This error message indicates that the component has not been deleted from the list.
Variable:
The lib_cmpnt is the library component type, such as LSM, DRIVE or CAP.
The cmpnt_id is the identifier of a library component, such as lsm_id, cap_id or drive_id.
User Response: Check the component indicated to see if a vary can correct the problem. If the error persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") contact Oracle Support.
Volume vol_id found in location_type location_id, reactivated with type=vol_type access_count=access_count pool=pool_id owner=owner_id.
Explanation: The specified volume was marked as absent or ejected in the database, but ACSLS found it in the library. The volume has been reactivated, and its critical information has been preserved.
Variable:
The vol_id is the absent or ejected volume.
The location_type is the location type (drive or cell) where the cartridge was found.
The location_id is the specific drive_id or cell_id where ACSLS found the cartridge.
The vol_type is the volume type (data, scratch or cleaning).
The access_count is the access count of the volume before it was marked absent.
The pool_id is the pool_id to which the volume belonged before it was marked absent.
The owner_id is the owner of the volume before it was marked absent.
User Response: None.
Volume vol_id, not found in location_type location_id and was marked absent.
Explanation: Each volume has a home cell and ACSLS can record it as mounted on a drive. ACSLS could not find the specified volume in its recorded location(s), and it has been marked absent in the database to preserve its critical information.
Variable:
The vol_id is the absent volume.
The location_type is the location type (drive or cell) where the volume was recorded and where ACSLS could not find it.
The location_id is the specific drive_id or cell_id where the volume was recorded but was not found.
User Response: None. An audit of the ACS or LSM may find the absent volume.
LSM lsm_id is full; volume vol_id cannot be recovered and is marked absent.
Explanation: ACSLS found this volume in the playground/in-transit cell or in a PCP cell while recovering an LSM. It attempted to recover the volume by moving it to a new home cell in this LSM. However, the volume could not be recovered, as the LSM was full, so the volume was marked absent in the database.
Variable:
The lsm_id identifies the LSM being recovered.
The vol_id identifies the absent volume.
User Response:
Eject a volume from the LSM.
Vary the LSM offline and back online to recover the volume.
LSM Misplaced cartridge detected, volume vol_id cannot be recovered and is marked absent.
Explanation: ACSLS found this volume in the playground/in-transit cell or in a PCP cell while recovering an LSM. It attempted to recover the volume by moving it to a new home cell in this LSM. However, the move failed because the destination cell contained a cartridge. The volume has not been recovered and is marked absent in the database
Variable: The vol_id identifies the absent volume.
User Response:
Check to make sure that the problem is not a single misplaced cartridge.
If it is not, audit the LSM to update the ACSLS database in order to watch the actual contents of the library.
Vary the LSM offline and back offline to recover the volume.
Volume identifer vol_id already found absent.
Explanation: The Manual Volume Delete utility (del_vol) was run for a volume that is already marked as absent in the database, but the delete option (-d) was not specified. The volume remains in absent status.
Variable: The vol_id identifies the absent volume.
User Response: None.
EXEC SQL Unable to mark volume vol_id as absent because of a database error.
Explanation: ACSLS could not find a volume in the library and attempted to mark it absent, but the ACSLS database interface returned an unusual status to the volumetable update. The database update failed.
Variable: The vol_id identifies the absent volume.
User Response:
Stop ACSLS (kill.acsss).
Stop the database (db_command stop).
Kill any hanging ACSLS processes.
Restart ACSLS (one time).
If the problem persists, you may need help in verifying that the table volumetable exists and that the acsss user has the proper permissions to update it. Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
EXEC SQL Unable to mark volume vol_id as ejected because of a database error.
Explanation: ACSLS ejected a volume and attempted to mark it as "ejected". The ACSLS database interface returned an unusual status to a volumetable update. The database update failed.
Variable: The vol_id identifies the ejected volume.
User Response:
Stop ACSLS (kill.acsss).
Stop the database (db_command stop).
Kill any hanging ACSLS processes.
Restart ACSLS (one time).
If the problem persists, you may need help in verifying that the table volumetable exists and that the acsss user has the proper permissions to update it. Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Volume vol_id was not found and will be marked absent.
Explanation: ACSLS did not find the specified volume in its home cell. If the volume was recorded as mounted on a drive, ACSLS did not find it on the drive. The volume will be marked absent in the database. An audit of the ACS or LSM may find the absent volume.
Variable: The vol_id identifies the volume that ACSLS did not find.
User Response: None.
program: Will attempt to dismount volume vol_id from drive drive_id.
Explanation: This message is issued when a possible cartridge stuck-in-drive condition is encountered during a failed mount request. The dismount attempts to recover the cartridge and drive.
Variable:
The program is the name of the program from which the message originates.
The vol_id is the identifier of the volume in this mount request.
The drive_id is the identifier of the drive in this mount request.
User Response: None. A dismount force request is automatically generated to recover the drive.
EXEC SQL lock timeout on delete from table.
Explanation: An attempt to delete a locked record from the database has failed.
Variable: The table is the name of the locked table
User Response: Restart the application server. If the problem persists, restart the database.
EXEC SQL delete from table failed.
Explanation: An attempt to delete records from the table failed.
Variable: The table is the name of the table.
User Response: Restart the application server - If the problem persists, restart the database.
EXEC SQL select count(col_name) from table failed.
Explanation: An attempt to count the number of records from the table has failed.
Variable:
The col_name is the name of one of the columns in the table.
The table is the name of the table.
User Response: Restart the application server. If the problem persists, restart the database
Illegal value illegal_port_number. Must be numeric.
Explanation: The number you entered for the port number is non-numeric.
Variable: The illegal_port_number is an invalid port number that was entered for use as the fixed port for inbound ACSLS client requests (in acsss_config).
User Response: Enter a valid numeric number.
Out-of-bounds value illegal_port_number:CSI_or SSI_INET_PORT.
Explanation: You have entered a value that is outside the legal range for the port for the ACSLS CSI or SSI networking component.
Variable: The illegal_port_number is an invalid port number that was entered for use as the fixed port for inbound ACSLS client requests (in acsss_config).
User Response: Enter a value between 1024 and 65535.
Unable to allocate socket for RPC TCP service.
Explanation: ACSLS was unable to allocate a socket for network communications. Causes are typically system resource related, such as too many open descriptors.
Variable: None.
User Response: See your System Administrator.
Unable to set SO_REUSEADDR on socket.
Explanation: ACSLS was unable to change a critical flag on the socket which would allow the socket to be reused for communications. This is usually related to system resource details.
Variable: None.
User Response: See your System Administrator
Unable to bind socket to port port_number.
Explanation: This indicates that the port was not bound to the socket. The most likely cause is that the port is already in use.
Variable: The port_number is the port number that was entered for use as the fixed port for inbound ACSLS client requests (in acsss_config).
User Response: Try changing the port number used by ACSLS for network communications to another (unused) port. See your System Administrator for assistance.
Failed on attempt to get socket name.
Explanation: ACSLS was unable to get the name of the socket that is used for network communications. The most likely cause is an internal systems fault.
Variable: None.
User Response: Restart ACSLS.
Lh error: routine_name: ACS acs_id: Re-sent txn count times but failed with error_code error. Dropping transaction.
Explanation: The attempt to send a library transaction was unsuccessful, and the maximum number of retries has been reached.
Variable:
The routine_name is the program routine reporting the problem.
The acs_id is the ACS that experienced the undeliverable transaction.
The count is the number of retries attempted.
The error_code is an internal four-digit error code (a two digit error category followed by a two digit error code).
User Response: If you see this message during product configuration, verify all hardware configuration and all hardware connections. Verify that network communications between the server and the library are working correctly.
If you see this occur during ACSLS operation:
Verify that the library is online to ACSLS and operational. You may need to vary the ACS and port offline, then back online, to reset library communications.
Check for related entries in the Event log for additional information about the error. It may be necessary to re-run an operation that was affected by the problem.
If necessary, restart ACSLS and if the problem persists collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
Rp error: routine_name: ACS acs_id: Invalid LSM number lsm_no in Catalog cell request from caller
Explanation: The attempt to examine the contents of a storage cell failed due to an invalid LSM identifier in the request being processed.
Variable:
The routine_name is the program routine reporting the problem.
The acs_id is the ACS which is reporting the problem.
The lsm_no is the invalid LSM number in the request.
The caller is the process or operation from which the request was received.
User Response: If you see this message during product configuration, verify all hardware configuration and all hardware connections. Verify that network communications between the server and the library are working correctly.
If you see this occur during ACSLS operation:
Verify that the library is online to ACSLS and operational. You may need to vary the ACS and port offline, then back online, to reset library communications.
Check for related entries in the Event log for additional information about the error. It may be necessary to re-run an operation that was affected by the problem.
If necessary, restart ACSLS and if the problem persists collect relevant ACSLS data. See "Gathering Diagnostic Information for Oracle Support". Then contact Oracle Support.
ACSLS database backup area unavailable.
Explanation: Requested backup directory not available.
Variable: None.
User Response: None.
For volume vol_id, the home cell cell_id has an inconsistent cell status cell_status. ACSLS will recover the cartridge automatically.
Explanation: An attempt was made to mount the specified volume, but its home cell had an inconsistent status. ACSLS will recover the cartridge automatically.
Variable:
The vol_id identifies the volume that was attempted to be mounted.
The cell_id identifies the volumes' home cell.
User Response: None. ACSLS will attempt to recover the volume and home cell automatically
Checking for LSM lsm_id status.
Explanation: This message is reported when the Library Handler sends an LSM Status request to the library as part of the process of ACSLS startup or bringing an ACS, LSM, or a drive online.
Variable: The lsm_id identifies the LSM for which status is requested from the library.
User Response: None. This message lets customers track the progress of ACSLS startup or bringing a library online.
LSM lsm_id lsm_ready_status lsm_state access_door_status hand_n operative_status, full_empty_status.
Variable:
The lsm_id identifies the LSM for which status was requested from the library.
The lsm_ready_status describes the Ready or Not Ready status of the LSM.
The lsm_state describes the on-line or off-line state of the LSM.
The access_door_status describes the access door status (open or closed).
The hand_n identifies each robotic hand in the LSM.
The operative_status describes the operative or inoperative status of the hand.
The empty_full_status describes the empty or full state of the hand.
User Response: None. This message lets customers track the progress of ACSLS startup or bringing a library online.
A drive in LSM acs_id,lsm_id is inoperative. Until this is corrected, the drives in this LSM cannot come online.
Explanation: The SL8500 may send a ”1002” error (drive not operational) in response to ”LSM Transport Status by Panel” request from ACSLS.
Variable:
The acs_id is the ACS identifier.
The lsm_id is the LSM identifier.
User Response:
Install the latest SL8500 microcode.
If this does not fix the problem, identify the drive that is causing the ”1002” error and remove that drive or replace that drive with a drive that is operational.
If the inoperative drive cannot be removed or replaced, then do not use the drives that are offline in acs_id, lsm_id.
LSM lsm_id not found in the configuration.
Explanation: The specified LSM was not found in the configuration.
Variable: Module is the ACSLS module displaying this message.
The lsm_id is the LSM that is not present in the configuration.
User Response: None.
Module: config_command command canceled.
Explanation: You cancelled the dynamic configuration utility config_command.
Variable: module processing the cancel command. Here, it is cfg_main.
config_command is the specific dynamic configuration request that you cancelled. It can be any one of the following:
config lsm lsm_id.
config acs new.
config acs acs_id.
config acs acs_id delete.
config port(s) acs_id.
User Response: None. You can re-enter the dynamic configuration command again.
Module: Volume vol-id re-entered into library to cell location_id, reactivated with type=vol_type access_count=access_count pool=pool_id owner=owner_id..
Explanation: The specified volume was marked as absent or ejected in the database, and is being re-entered into the library. The volume was re-activated, and its critical information was preserved.
Variable: Module is the ACSLS module displaying this message
The vol_id is the absent or ejected volume.
The module is the ACSLS module displaying the message.
The location_id is the new home location, where ACSLS moves the cartridge that is being re-entered.
The vol_type is the volume type (data, scratch, or cleaning).
The access_count is the access count of the volume before it was marked absent.
The pool_id is the pool_id to which the volume belonged before it was marked absent.
The owner_id is the owner of the volume before it was marked absent.
User Response: None.
Modifier: LSM READY received for LSM identifier lsm_id, Modifier modifer_number.
Explanation: The LSM has been placed online.
Variable: Modifier is the ACSLS module displaying this message.
The lsm_id is the LSM identifier of the LSM that is online.
The modifier_number is the LSM READY modifier and can have the following values:
1 for LSM Ready Normal.
2 for LSM Recover Intransit cartridge.
3 for LSM Ready with CAP Open.
User Response: None.
New robotic hand hand_id detected in LSM lsm_id; and added to the database.
Explanation: ACSLS detected a new robotic hand in the LSM and added this hand to the handtable in the database.
Note:
When robotic hands are removed from the library, the records from these hands are not removed from the database.Variable: The lsm_id is the LSM identifier; hand_id is the hand identifier.
User Response: None.
DB status [db_status] detected on cap mode update.
Explanation: An attempt to update cap_mode to manual in ACSLS database failed.
Variable: The db_status identifies the status returned by database.
User Response: Restart the application server. If the problem persists, restart the database.
EXEC SQL Lock timeout on update captable.
Explanation: An attempt to update cap_mode to manual mode in ACSLS database failed.
Variable: None.
User Response: Restart the application server. If the problem persists, restart the database.
Additional Connect request received for port port_id that is already connected. Request ignored.
Explanation: When a second connect request was received by SCSI libraries the request was ignored and the warning message was logged into the product log.
Variable: The port_id is the identifier of the ACSLS-to-library port.
User Response: None.
LSM lsm_id type changed from lsm_type_db to lsm_type_lib; LSM remains offline.
Explanation: LSM type changed from lsm_type_db to lsm_type_lib and LSM status reported is NOT READY. LSM will be marked offline.
Variable:
The lsm_id is the LSM identifier whose type has changed.
The lsm_type_db is the LSM type as present in database.
The lsm_type_lib is the LSM type as reported by library.
User Response: Determine why the LSM is not ready, and address the problem to bring the LSM online.
Please update your ACSLS library configuration using Dynamic Config or acsss_config.
Explanation: The library configuration for ACS acs_id or LSM lsm_id has changed. The ACS or LSM involved remains offline [diagnostic] until the ACSLS configuration is updated.
Variable: None.
User Response: Use Dynamic Config or acsss_config to update the ACSLS configuration for this ACS or LSM.
Invalid ACSLS database version acsls_db_version. Must be less than or equal to max_supported_db_version.
Explanation: The ACSLS database version being imported is not supported by this ACSLS release.
Variable:
The acsls_db_version is the version number to which the ACSLS database was exported.
The max_supported_db_version is the highest database version which can be imported to this ACSLS release.
User Response:
Export the previous ACSLS database in a format supported by this ACSLS release.
Import the compatible version of the database.
cl_ipc_read: Invalid packet parameters, host_id.
Explanation: A packet has been received with unrecognized parameters. The packet will be ignored.
Variable: None.
User Response: Watch for related message 2638. If an unknown internet source is attempting to submit traffic to this port, contact your local network security administrator.
lm_input: Invalid format of message received. Message ignored.
Explanation: This message will likely be seen with message 2566. The message will be dropped.
Variable: None.
User Response: See Message 2566.
%s Cannot connect to Library manager database. Status code (%d).
Explanation: Cannot connect to the database.
Variable: The %s is the name of the file.
User Response: None.
ACSLS recovery initiated.
Explanation: Initiating database recovery process.
Variable: None.
User Response: None.
ACSLS backup started.
Explanation: Backup of ACSLS started.
Variable: None.
User Response: None.
ACSLS recovery started.
Explanation: Restore of ACSLS started.
Variable: None.
User Response: None.
cl_ipc_read: Message from unknown Internet host ignored.
Explanation: A packet from an unauthorized host has been received by ACSLS. Since the host-id is not recognized, the packet will be ignored.
Variable: None.
User Response: If this message persists, contact your local Network security administrator. You can extract more information about the intruding packets with 'snoop'. As 'root' run the command 'snoop port 50003'.
ACSLS recovery failed.
Explanation: Recovery of ACSLS failed.
Variable: None.
User Response: None.
ACSLS recovery aborted. ACSLS database and control files are not restored.
Explanation: Restore aborted due to some signal interference. Signal was received before starting ACSLS database or control files.
Variable: None.
User Response: None.
ACSLS recovery aborted. ACSLS database and control files are in an inconsistent state. ACSLS startup may fail. Perform a fresh recovery to avoid unforeseen errors.
Explanation: Restore aborted due to some signal interference. Signal was received when ACSLS database or control files recovery is in progress. ACSLS cannot be used and a fresh restore is needed.
Variable: None.
User Response: None.
ACSLS database and control files recovery completed.
Explanation: Successful recovery of database and control files.
Variable: None.
User Response: None.
ACSLS recovery aborted. ACSLS database is not restored.
Explanation: Restore aborted due to some signal interference. Signal was received before the start of ACSLS database recovery.
Variable: None.
User Response: None.
ACSLS recovery aborted. ACSLS database is in an inconsistent state. ACSLS startup may fail. Perform a fresh recovery to avoid unforeseen errors.
Explanation: Restore aborted due to some signal interference. Signal was received when ACSLS database recovery is in progress. ACSLS cannot be used and a fresh restore is needed.
Variable: None.
User Response: None.
ACSLS recovery completed.
Explanation: Restore successful.
Variable: None.
User Response: None.
ACSLS recovery aborted. ACSLS control files are not restored.
Explanation: Restore aborted due to some signal interference. Signal was received before the start of control files recovery.
Variable: None.
User Response: None.
ACSLS recovery aborted. ACSLS control files are in an inconsistent state. ACSLS startup may fail. Perform a fresh recovery to avoid unforeseen errors.
Explanation: Restore aborted due to some signal interference. Signal was received when control files recovery is in progress. ACSLS cannot be used and a fresh restore is needed.
Variable: None.
User Response: None.
ACSLS backup aborted. ACSLS database and control files are not backed up.
Explanation: Backup aborted due to signal interference. Signal was received when backup of control files or database is in progress.
Variable: None.
User Response: None.
ACSLS backup aborted. ACSLS backup tape will not be usable.
Explanation: Backup to tape aborted due to signal interference. Signal was received when backup of control files or database is in progress.
Variable: None.
User Response: None.
A fully qualified host name for hostname is not found in /etc/hosts.
Explanation: The routine searched the system /etc/hosts file looking for a fully qualified expression for the name of the local host machine. A fully qualified expression takes the form: somehost.somedomain.com.
Variable: None.
User Response: The PostgreSQL database requires that the fully qualified host name of the local machine appears in the local /etc/hosts file. Typically, the expression is found in the second field of the loghost record. For example:
127.65.43.21 myhost.mydomain.com myhost loghost
Java version %s is downlevel! Minimum java version version %s is required for ACSLS.
Explanation: ACSLS cannot work with the currently configured Java version.
Variable: The %s is the Java version level.
User Response: Consult the ACSLS Installation Guide to determine the correct Java version and the procedure for installing it.
Java version %s is downlevel! Setting link /usr/java to %s.
Explanation: While the configured Java version was down level, the script was able to find a compatible version on the system. It automatically changed the /usr/java link to point to the Java version required for ACSLS.
Variable: The %s is the Java version level.
User Response: No action is required unless you have installed other applications that employ a down-level Java version. In such cases, you will need to resolve the discrepancy either by upgrading the conflicting application, setting a different pointer to the Java version required by that application, or removing the conflicting application from the system.
Received incorrect byte count from input socket: byte_count.
Explanation: An internal communication between components has failed.
Variable: The byte_count is the count of bytes read.
User Response: Retry the command.
Received invalid request type: req_type.
Explanation: An internal communication between components has failed.
Variable: The req_type is the value of the invalid request.
User Response: Retry the command.
Received invalid Sense Code: sense_code.
Explanation: An internal communication between components has failed.
Variable: The sense_code is the value sent by the hardware.
User Response: Retry the command.
Received invalid Status request type: req_type
Explanation: An unexpected response was detected from the hardware.
Variable: The req_type is the value of the invalid status request.
User Response: Collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Unexpected LH failure. Sense code is sense_code.
Explanation: An unexpected response was detected from the hardware.
Variable: The sense_code is the value sent by the hardware.
User Response: Verify that the hardware is online. Check the LSM logs for more information.
Unexpected LSM failure. Sense code is sense_code.
Explanation: An unexpected response was detected from the hardware.
Variable: The sense_code is the value sent by the hardware.
User Response: Verify that the hardware is online. Check the LSM logs for more information
Received 0 bytes from device: dev_name.
Explanation: The SCSI device driver may not have been properly installed.
Variable: The dev_name is the name of the device being opened, such as /dev/mchanger4.
User Response: Verify that the hardware is online. Check the LSM logs for more information.
No data received after forking process.
Explanation: The scsiLh was not able to communicate with the scsiDP. The SCSI device driver may not have been properly installed.
Variable: None.
User Response: Verify that the hardware is online. Check the LSM logs for more information.
Failed to create UNIX process for device: dev_name.
Explanation: The scsilh_im was not able to communicate with the scsiDP.
Variable: The dev_name is the name of the device being opened, such as /dev/mchanger4.
User Response: Restart ACSLS and if the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Failed to set up read/Wait for process.
Explanation: The scsiLh encountered an internal error.
Variable: None.
User Response: Restart ACSLS and if the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support
Starting new UNIX process dev_name
Explanation: The scsiDP died and was restarted by the scsilh_im.
Variable: The dev_name is the name of the device being opened, such as /dev/mchanger4.
User Response: Retry the command. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Received incorrect byte count from shared memory: byte_count.
Explanation: An internal communication between components has failed.
Variable: The byte_count is the count of bytes read.
User Response: Retry the command. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Error received from call to smc library: error_code.
Explanation: An internal communication between components has failed.
Variable: The error_code is the error code returned by the smc library.
User Response: Retry the command. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Failed to write to socket: socket_name.
Explanation: An internal communication between components has failed.
Variable: The socket_name is the name of the socket.
User Response: Retry the command. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Timed out on request: req_name.
Explanation: The hardware took longer than expected to respond.
Variable: The req_name is the name of the request.
User Response: Verify that the hardware is online. Check the LSM logs for more information. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Received too many (nnn) bytes in response to internal command: req_name.
Explanation: An internal communication between components has failed.
Variable:
The nnn is the number of bytes received.
The req_name is the count of bytes read.
User Response: Retry the command. If the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Unexpected startup data received from process: aString.
Explanation: An internal communication between components has failed.
Variable: The aString is the string that was read from the hardware.
User Response: Verify that the hardware is online. Check the LSM logs for more information. Retry the command, and if the problem persists, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Support.
Recovering scsiDP: aString.
Explanation: A communication error occurred between the library and ACSLS.
Variable: The aString is the scsiDP process description.
User Response: None. If you see these messages frequently, you may be experiencing cable problems.
Tried to access drive while cleaning cartridge installed.
Explanation: An attempt was made to mount a cartridge while a cleaning cartridge was in the process of cleaning the drive.
Note:
This message is for a SCSI/Fibre-attached library, where the library automatically cleans tape drives.Variable: None.
User Response: None. ACSLS should automatically retry the mount.If the number of mount retries is exceeded and the ACSLS automatic retries fail, re-issue the mount command.
Logical ACS logical_acs_id (name) added using physical ACS acs_id.
Explanation: A logical library was created by the administrator.
Variable:
The logical_acs_id is the logical ACS number assigned to the new logical library.
The name is the name specified for the logical library.
The acs_id is the ACS identifier of the physical library.
User Response: None.
Logical ACS logical_acs_id removed.
Explanation: A logical library was removed from the configuration and is no longer available for client access. Any drives and volumes in that logical library are unassigned and are available for ACSAPI use, or for assignment to another logical library.
Variable: The logical_acs_id identifies the logical library which was removed.
User Response: None.
Logical Drive logical_location (serial_number) added using physical Drive drive_id.
Explanation: A drive has been assigned to a logical library. A logical location is automatically assigned to the drive. The drive is no longer available for ACSAPI use or for assignment to another logical library.
Variable:
The logical_location identifies the logical location assigned to the drive.
The serial_number identifies the serial number of the drive (if available).
The drive_id identifies the physical drive.
User Response: None.
Logical Drive logical_location removed.
Explanation: A drive has been unassigned from a logical library. This frees a drive slot, to which another drive can now be assigned. The drive is now available for ACSAPI use or for assignment to another logical library.
Variable: The logical_location identifies the logical location which had been assigned to the drive.
User Response: None.
Initiator initiator removed.
Explanation: An initiator (FC client port) which was connected to the ACSLS server has been removed from the database by the administrator. The ability to remove initiators allows the deletion of obsolete entries for clients that are no longer connected.
Variable: The initiator is the FC client (identified by WWN and alias) which was removed.
User Response: None. ACSLS automatically (re-)adds initiators if they are detected on any configured ACSLS target port.
Target target removed.
Explanation: A FC port which was configured for target mode operations on the ACSLS server has been removed from the database by the administrator. The ability to remove targets allows the deletion of obsolete entries that are no longer configured.
Variable: The target is the FC target port identified by its WWN and its alias.
User Response: None. ACSLS will automatically (re-)add targets if they are configured for target mode operations using the getHba.sh utility.
Mapping added to logical_acs_id for (initiator,target,lun).
Explanation: A mapping was created to make a logical library visible to an FC client. A mapping defines the target port and LUN on which the client will see the logical library.
Variable:
The logical_acs_id is the logical ACS number for which the mapping was added.
The initiator is the FC client identified by its WWN and its alias.
The target is the FC target port identified by its WWN and its alias.
The lun is the LUN (logical unit number) associated with this client connection.
User Response: None. The logical library is now available for client use (client system configuration may be needed to detect the library).
Logical Volume vol_id mounted from logical drive logical_location..
Explanation: A mount operation involving a volume and drive (both assigned to a logical library) has been performed by an FC client.
Variable:
The vol_id identifies the volume which was mounted.
The logical_location identifies the logical location of the drive.
User Response: None.
Logical Volume vol_id dismounted from logical drive logical_location.
Explanation: A dismount operation involving a volume and drive (both assigned to a logical library) has been performed by an FC client.
Variable:
The vol_id identifies the volume which was dismounted.
The logical_location identifies the logical location of the drive.
User Response: None.
Logical Volume vol_id moved to new home location logical_location.
Explanation: A volume in a logical library has been moved to a new storage location by an FC client operation.
Variable:
The vol_id identifies the volume which was moved.
The logical_location identifies the new logical location of the volume.
User Response: None.
Logical Volume vol_id ejected from logical ACS logical_acs_id.
Explanation: A volume in a logical library has been moved to an import/export location by an FC client operation. The logical status of the volume is updated to reflect this operation, and the volume is no longer accessible to that client.
Note:
No physical eject operation is performed, and the volume is not unassigned from the logical library.Variable:
The vol_id identifies the volume which was moved.
The logical_acs_id is the logical ACS number to which the volume is assigned.
User Response: None. The volume can be physically ejected if desired, but remains assigned to the logical library. If the volume is then re-entered, it becomes accessible to the client.
Logical Volume vol_id corrected for eject.
Explanation: ACSLS detected that a physical eject operation has taken place, involving a volume which is assigned to a logical library. The logical status and location of the volume are updated to reflect this operation. The volume remains assigned to the logical library, but is inaccessible for client operations.
Variable: The vol_id identifies the volume that was updated.
User Response: None. If the volume is re-entered, it becomes accessible to the client
Logical Volume vol_id corrected for enter (new location is logical_location).
Explanation: ACSLS detected that a physical enter operation has taken place, involving a volume which is assigned to a logical library. A new logical location is assigned to the volume and it is now available for FC client operations.
Variable:
The vol_id identifies the volume which was updated.
The logical_location identifies the new logical location of the volume.
User Response: None.
Logical Volume vol_id corrected for mount (new location is logical_location).
Explanation: ACSLS detected that a physical mount operation has taken place involving a volume which is assigned to a logical library. The logical status and location of the volume is updated to reflect this operation.
Variable:
The vol_id identifies the volume that was updated.
The logical_location identifies the new logical location of the volume.
User Response: None.
Logical Volume vol_id corrected for dismount (new location is logical_location).
Explanation: ACSLS detected that a physical dismount operation has taken place, involving a volume which is assigned to a logical library. The logical status and location of the volume is updated to reflect this operation.
Variable:
The vol_id identifies the volume which was updated.
The logical_location identifies the new logical location of the volume.
User Response: None.
Response received but packet size too small (byte_count should be at least min_size); Dropping packet!
Explanation: The ACSLS GUI has received a message that is too small from ACSLM. The GUI did not attempt to interpret the message because it did not have enough information. This could be a problem with either the network or the software
Variable:
The byte_count is the number of bytes in the message.
The min_size is the minimum size of a valid, readable message.
User Response: Make sure the problem is not caused by a network issue. If the problem is not a network issue, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.
Response received for unknown sequence number sequence_num; Dropping packet!
Explanation: The ACSLS GUI received a response from ACSLS, but the sequence number was not associated with any existing request. The response is ignored.
Variable: The sequence_num is the sequence number contained in the response packet.
User Response: None.
Communication with ACSLM at internet_addr: port_num setup.
Explanation: An IPC communication link has been established between the ACSLS GUI and the ACSLM process. This link is used to perform library operations that are requested by a GUI operator.
Variable:
The internet_addr is the address of the server on which ACSLM is running.
The port_num is the port number used to identify the ACSLM process
User Response: None.
SMCE startup beginning.
Explanation: The SMCE subsystem is beginning its initialization processing. This subsystem provides support for commands issued by FC clients.
Variable: None.
User Response: None.
SMCE startup complete.
Explanation: The SMCE subsystem has completed its initialization processing. Commands from FC clients can now be accepted.
Variable: None.
User Response: None.
SMCE mapping: Initiator: initiator, Target: target, Lun: lun, acsID: logical_acs_id.
Explanation: A Unit Attention was raised to signal a startup event (Not Ready-to-Ready Transition) to any FC client that has access to a logical library. This informs the client that the logical library has become operational after being unavailable for some period of time.
Variable:
The initiator is the FC client identified by its WWN and its alias.
The target is the FC target port identified by its WWN and its alias.
The lun is the LUN (logical unit number) associated with this client connection.
The logical_acs_id is the logical ACS number of the logical library.
User Response: None.
SMCE shutdown requested.
Explanation: The SMCE subsystem is beginning its shutdown processing. Commands from FC clients can not be accepted if this subsystem is shutdown.
Variable: None.
User Response: None. To resume FC client support, issue the acsss enable command
SMCE shutdown complete.
Explanation: The SMCE subsystem has completed its shutdown processing. Commands from FC clients can not be accepted if this subsystem is shutdown.
Variable: None.
User Response: None. To resume FC client support, issue the acsss enable command.
SMCE terminated abnormally.
Explanation: An unrecoverable error has occurred during startup or execution of the SMCE subsystem. This subsystem is required to support FC client operations.
Variable: None.
User Response: The SMCE subsystem should automatically be restarted by the Solaris Service Management Facility (SMF). Verify that the smce service is online using the acsss status command. If the service is not online, check for errors or diagnostic information in the service log file. The log file location can be obtained using the acsss l-status command.
SMCE command failed abnormally.
Explanation: An error has occurred during execution of a SCSI Media Changer command which was received from a FC client. The command may not have been successfully completed, or it may have been completed but the SMCE subsystem was unable to deliver a final response to the client.
Variable: None.
User Response: Check the client system for information regarding failed operations. Retry the failed operation from the client system, if needed.The problem may be caused by FC connectivity issues between the client and the ACSLS server. Verify that the client operating system can still see the logical library device. Re-configuration of the client software may be needed.
If the client can see the logical library, but problems persist when trying to execute commands, collect relevant ACSLS data (see "Gathering Diagnostic Information for Oracle Support") and contact Oracle Support.