Status Codes for Script Execution
This section provides a list of status codes for scheduled server-side script execution. These are displayed in the Status Message column of the Script/Job Monitor.
Codes for Script Groups
| Code | Message |
|---|---|
|
0 |
New |
| 10 |
Unscheduled Displayed for script groups that are stored, but not scheduled. |
| 50 |
Completed Displayed for script groups that have executed successfully. |
| 100 |
Scheduled Displayed for script groups that are scheduled and waiting to run. |
| 200 | Active |
| 300 | Interrupted |
Codes for Unscheduled Scripts
| Code | Message |
|---|---|
|
110 |
Unscheduled Displayed for scripts that are stored, but not scheduled. |
Codes for Completed Scripts
| Code | Message |
|---|---|
|
210 |
Completed Displayed for scripts that have executed successfully. |
|
220 |
Completed with Warnings Displayed for scripts that have executed with one or more warnings (but no errors). |
|
230 |
Completed with Errors Displayed for scripts that have executed, but with one or more errors (and possibly warnings). |
Codes for Scripts that Are No Longer Running
| Code | Message |
|---|---|
|
310 |
Canceled by request Displayed for executing scripts that have been canceled by the user. |
|
320 |
Aborted Displayed for scripts that have been aborted due to an error. An error message is also displayed. |
|
324 |
Aborted no restart Displayed for live reorganization and partitioning scripts that cannot be restarted. This status is displayed after an attempt to restart a script is made. Usually, it indicates that a QUEST_EXEC command is not scripted correctly. It can also indicate that a LiveReorg object or control structure needed by QSA is missing. For help in cleaning up LiveReorg objects, contact Quest Software Support. Once cleanup is performed, a new script can be generated for objects in the failed script. |
|
325 |
Aborted restart Displayed for live reorganization and partitioning scripts that cannot be restarted. This status is displayed after an attempt to restart a script is made. Usually, it indicates that a LiveReorg object or control structure needed by the QSA is missing. For help in cleaning up LiveReorg objects, contact Quest Software Support. Once cleanup is performed, a new script can be generated for objects in the failed script. |
|
350 |
Aborted internal Displayed for scripts that failed due to a fatal internal error. Information on the error is displayed in the script execution log. |
|
360 |
Aborted timeslot Displayed for scripts that did not start within 10 minutes of their scheduled time. There is a 10-minute time window for the start of script execution. If QSA is running or started during this time window, a script is executed by QSA. If QSA is started after the time window ends, a script is aborted. Reschedule the script or run it using the Execute function available in the Scripts/Job Monitor. Check the monitor to see QSA’s status. |
Codes for Halted and Scheduled Scripts
| Code | Message |
|---|---|
|
370 |
Halted for datafile maintenance Displayed by default for scripts that have been paused for datafile maintenance or another purpose. Your own reason for a pause is displayed after “Halted for…” if you entered one when you selected the script-pause option. This option was available for standard reorganizations with Reorg Manager in previous releases (8.0.2 or earlier) of Space Manager. |
| 410 |
Scheduled Displayed for scripts that are scheduled and waiting to run. |
Codes for Executing Scripts
| Code | Message |
|---|---|
|
510 |
Executing Displayed for scripts that are currently executing. |
| 515 |
Processing with posting paused |
Codes for LiveReorg Scripts
| Code | Message |
|---|---|
|
520 |
Posting live modifications Displayed for live reorganization scripts for which live updates made to the original tables are being posted to reorganized copy tables. |
|
610 |
Blocked Displayed for live reorganization scripts that are waiting to obtain a lock on one or more tables that are locked by another session. Tables are locked briefly at the beginning of the data copy stage of a live reorganization. They are also locked briefly during the switch from reorganized table to copy table when the T-Lock switch style is used. |
|
620 |
Waiting until Day/Date/Time Displayed for live reorganization scripts that are waiting for a user-specified time window to make the switch from original tables to reorganized copy tables. |
|
630 |
Waiting for approval Displayed for displayed for live reorganization scripts that are waiting for the user to approve the switch from an original table to a reorganized copy table. |
Error Messages
This section provides a list of the error messages generated by QSA. The description for each error includes cause and recommended action. Most QSA error messages are displayed in the Status Message column of the Scripts/Job Monitor.
Oracle errors are also displayed in the Scripts/Job Monitor. For more information on Oracle errors, see the Oracle documentation and Common Oracle Errors Found in Script Execution.
Note Most QSA error messages have a prefix of “QSA”. The error messages QSA generates for FastCopy have a prefix of “FC”.
QSA Server Agent Errors (20300 – 20359)| Error | Cause | Action |
|---|---|---|
|
QSA-20301 Server not available / No response from server |
QSA is not installed or not running. This error also occurs if you try to stop QSA when you are not connected to the instance on which it is installed in an active-active OPS or RAC environment. |
Install QSA again or start it. See Start QSA Using the Admin Function for more information. If QSA still doesn’t start, examine the QEXECD.LOG file located in $INSTALL_DIR/log (where INSTALL_DIR is the installation directory for QSA). If you are trying to stop QSA in an active-active OPS or RAC system, first connect to the instance on which it is installed. |
|
QSA-20302 No such script |
An attempt was made to schedule a script that does not exist in the QUEST_SCRIPT table. | Make sure the correct folder name, owner name, and script_id are specified for the script when you store it. |
|
QSA-20303 Script already running |
An attempt was made to unschedule a script currently being executed. | Consider canceling the script. This will stop execution. You can then unschedule or reschedule the script. |
|
QSA-20304 Script not running |
An attempt was made to cancel a script not currently being executed. Only running scripts can be canceled. | Check the status of the script and cancel it when its status is displayed as Executing. |
|
QSA-20305 Script not waiting |
An attempt was made to approve a script that is not waiting for approval for the switch from original table to reorganized copy table. | Continue checking the status of the script and give approval when its status is displayed as Waiting for approval or Waiting until day/date/time. |
|
QSA-20306 Script is not scheduled |
An attempt was made to unschedule a script that is not scheduled for execution. | Check the status of the script. No action is necessary. |
|
QSA-20307 Function not implemented |
An attempt was made to use a QSA function that has not been implemented. | Contact Quest Software Support. |
|
QSA-20308 No such log file |
An attempt was made to retrieve a log file that does not exist. This can occur when log files are purged due to aging. | Try the operation again. If you get repeated failure, contact Quest Software Support. |
|
QSA-20309 Owner, folder and script cannot contain certain characters |
The owner name, folder name, or script_id specified for a script contains a period, quote, forward slash, or backward slash. These characters are not allowed. | Specify an owner, folder, or script_id without a period, quote, forward slash, or backward slash. |
|
QSA-20311 Table conflict with script already executing |
This error can occur when: A script includes a table that is also included in a script that is currently executing. A script includes a table with referential integrity on tables in a script that is currently executing. BEQUEATH_DETACH is set to No in the SQLNET.ORA file. |
Wait until the currently executing script has completed before executing a conflicting script or set BEQUEATH_DETACH to Yes in the SQLNET.ORA file. |
|
QSA-20312 Scheduled launch time expired |
A script was not executed when its scheduled time occurred, most likely because the server host or QSA was not available at that time. (QSA prohibits script execution at a time other than the one scheduled. This prevents unintended execution.) | Reschedule the script. |
|
QSA-20313 Invalid login name for daemon |
The username or password for the Oracle account that installed QSA was changed after installation. QSA uses this account to log in to the database. When the password is changed, QSA can no longer log in. The error is displayed in the QSA log file after username or password is changed and QSA is restarted. |
Uninstall QSA and then reinstall it using the new credentials for the Oracle account. |
|
QSA-20314 Active jobs in progress |
An attempt was made to stop QSA while one or more scripts were being executed. | Wait until all scripts have completed or cancel all scripts that are being executed. Then stop QSA. |
|
QSA-20315 Daemon running |
An attempt was made to start QSA while it was already running. There should only be one QSA daemon or service running per database instance. | If the current QSA daemon or service is unusable, contact Quest Software Support. |
|
QSA-20316 Couldn’t start the daemon |
QSA could not be started. | Check the QEXECD.LOG file to determine why QSA could not be started. Fix the problem, then try to start QSA again. |
|
QSA-20317 Attempt to schedule script in the past |
An attempt was made to schedule a script for a date and time in the past. Scripts cannot be scheduled to start in the past. | Reschedule the script for a date and time that occur after the current date and time. |
|
QSA-20318 Script is already scheduled |
An attempt was made to schedule a script, which is already scheduled. | Check the status of the script. |
| Error | Cause | Action |
|---|---|---|
|
QSA-20360 Oracle error during installer SQL |
An Oracle error occurred during processing of one of the SQL scripts used to install, upgrade, or uninstall QSA. The cause may be conditions in the database or problems with the script. The Oracle error displayed along the QSA error helps identify the cause. | If the cause is lack of database resources, correct the problem and then try to install, upgrade, or uninstall QSA again. If the cause appears to be problems with the script, contact Quest Software Support. |
|
QSA-20361 Can’t parse QSAVersion.txt file |
The install script for QSA could not correctly parse the QSAVersion.txt file. | Contact Quest Software Support. |
|
QSA-20362 Oracle version not supported |
An attempt was made to install, upgrade, or uninstall QSA against an Oracle database version that is not supported. | If the Oracle version is one that is supported, contact Quest Software Support. |
|
QSA-20363 Product not installed |
An attempt was made to uninstall QSA when it is not installed. | If QSA is installed, contact Quest Software Support. |
|
QSA-20364 Can only upgrade or uninstall as installing UNIX user |
An attempt was made to upgrade or uninstall QSA as a UNIX user who is not the installing UNIX user or root. | Upgrade or uninstall QSA as the user who installed it or as root. |
|
QSA-20365 Can only upgrade or uninstall as installing Oracle user |
An attempt was made to upgrade or uninstall QSA as an Oracle user who is not the installing Oracle user. | To identify the installing Oracle user, check the owner of the QUEST_EXEC_PARAMETER table. Then upgrade or uninstall QSA as that user. |
|
QSA-20370 Required files are missing |
Required files such as text, script, and shell script files were not found on the Space Manager client PC from which installation of QSA is being performed. | Reinstall the Space Manager client. |
|
QSA-20371 This user does not have DBA status |
The Oracle account used for installing QSA does not have DBA privileges. This account used must be a DBA account with ALTER, CREATE, DROP, and EXECUTE privileges on all objects in the database QSA is being installed for. It must also have the UNLIMITED TABLESPACE system privilege. |
Log in as a DBA user with the privileges listed above. |
|
QSA-20372 Required components not found |
The Quest common objects are not found on the database server. | Reinstall Space Manager server components. |
|
QSA-20373 Required Quest Script version not found |
The Quest Script package is not installed on the database server or is an earlier version than the one required by QSA. | Reinstall Space Manager server components and QSA. |
|
QSA-20374 Cannot stop the daemon |
An attempt to stop QSA failed because a live reorganization script is being executed. | Wait until the script completes. Then try to stop QSA. |
|
QSA-20375 Cannot start the daemon |
An attempt to start QSA failed during installation of QSA. | Cancel the installation and check with a system administrator to determine if there are system problems. Once any problems are resolved, try to install QSA again. |
|
QSA-20376 Login ID not valid |
The login name of the UNIX account used for installing QSA is not valid. | Enter a valid UNIX login name. |
|
QSA-20377 This Operating System is not supported |
An attempt was made to install QSA on an operating system that is not supported. | Cancel the installation. |
|
QSA-20378 Root configuration failed |
An attempt by root to install QSA failed. | Contact Quest Software Support. |
|
QSA-20379 Root cleanup failed |
An attempt by root to uninstall QSA failed. | Contact Quest Software Support. |
|
QSA-20380 Path invocation error |
The installation script for QSA was not invoked as ./SCRIPT_NAME. It must be invoked as ./SCRIPT_NAME. | If this error occurs more than once, contact Quest Software Software Support. |
|
QSA-20381 Invalid arguments |
An attempt was made to start the QSA installation script with incorrect arguments. | If this error occurs more than once, contact Quest Software Support. |
|
QSA-20382 Unknown architecture type |
An attempt was made to install QSA on an operating system that is not supported. | If this error occurs more than once, contact Quest Software Support. |
|
QSA-20383 Could not create configuration file |
The QEXECD.CONF file could not be created. This file stores configuration information for QSA. The problem could be due to lack of disk space or permission. | If this error occurs more than once, contact Quest Software Support. |
|
QSA-20384 Must be root |
An attempt was made to invoke the ROOT.SH installation script or ROOT_UNINSTALL.SH uninstallation script by an account other than root. These scripts must only be invoked by the root user. This is because they require root privileges to install files into the /ETC and /SBIN directories. | Log in as root (or su) and invoke the script again. |
|
QSA-20385 Config file doesn’t exist |
The QEXECD.CONF file could not be found. This file stores configuration information for QSA. | If this error occurs more than once, contact Quest Software Support. |
|
QSA-20386 Invalid ORACLE_HOME |
An invalid ORACLE_HOME was specified during installation of QSA. This is the default base directory for QSA. When an invalid directory is specified, QSA cannot find the LIBCLNTSH library with which it is dynamically linked. The LIBCLNTSH library is supplied by Oracle and should reside in $ORACLE_HOME/lib. | Check the value of ORACLE_HOME. If installation is being performed using the installation wizard for QSA, check the value of ORACLE_HOME in your /ETC/ORATAB or /VAR/OPT/ORACLE/ORATAB file. |
|
QSA-20387 Do not invoke this script |
An attempt was made to execute a shell script that is intended for internal use by QSA. | Contact Quest Software Support. |
| Error | Cause | Action |
|---|---|---|
|
QSA-20390 An underlying OS error occurred |
An operating system error occurred. The cause may be a temporary lack of resources on the server host. | Execute the script again. If the problem occurs more than once, contact Quest Software Support. |
|
QSA-20390 Can't copy <src_file> to <dest_file> |
During manual installation of QSA on UNIX, the install script was not able to copy a file to the right location. | Make sure you are logged in as the user who initially installed QSA. Make sure the installing user has permission to write to all directories in the installation path. Check to see if the disk is full. |
|
QSA-20391 ORA - <nnnnn> during internal SQL |
An Oracle error occurred while internal SQL was being processed. The cause can fall into either of two categories. These are conditions in the database and problems experienced by QSA. The Oracle error number displayed in the message helps identify the cause of the error. | Check the script execution log generated by QSA to see a description of the Oracle error. Then take action based on information in the description. |
|
QSA-20391 Cannot identify Oracle version |
The version of QSA being installed is not compatible with the version of Oracle installed. | Contact Quest Software Support. |
|
QSA-20392 Internal error in script engine |
A function based index is the most selective index available for a table and was chosen by Space Manager as the posting index during a live reorganization. However, function based indexes cannot be used as posting indexes. | Reorganize the table using standard reorganization. If you want to perform a live reorganization for the table, give it a more selective index than the function based index. |
|
QSA-20392 Internal error: Invalid install type |
During a manual installation on UNIX, the install script could not determine whether the install option requested was Install, Update, or Uninstall. | Contact Quest Software Support. |
|
QSA-20392 Internal error (ORACLE_SID not defined) |
The ROOT.SH install script could not determine the ORACLE_SID from the QEXECD.CONF file. | Contact Quest Software Support. |
|
QSA-20393 Must be run under QSA Server Agent |
An attempt was made to run a script from the client or other environment when it should be run by QSA. Live reorganization scripts and scripts that use FastCopy or parallel QSA processes must be run by QSA. | Store and schedule the script for execution by QSA. You can work from the Script/Job Monitor to do this. |
|
QSA-20394 Could not create temporary QSA object in <LW_TABLESPACE> |
The tablespace used for LiveReorg objects does not have enough free space. The tablespace is specified with QSA’s LW_TABLESPACE parameter. QSA creates and uses LiveReorg objects during a live reorganization and drops them after the switch. |
Provide the space needed by increasing datafile size for the tablespace, adding a datafile to the tablespace, or setting the Autoextend property to On. All can be done from Tablespace Properties. An alternative action is to specify a tablespace with more free space for the LW_TABLESPACE parameter. This is done from the QSA Installer. After taking any of these actions, restart the script from the Script/Job Monitor. |
|
QSA-20395 Could not parse script |
A character in an object or owner name could not be converted to UNICODE. During script execution in databases that use multibyte character sets, QSA converts QUEST_EXEC commands to UNICODE. Characters in names are also converted. They are converted back to their database character set before reorganization is complete. There are a few characters that QSA cannot convert to UNICODE. After a script fails due to a conversion problem, the character that could not be converted is displayed in the script execution log or in QSA’s log (QEXECD.LOG). | Contact Quest Software Support. |
| Error | Cause | Action |
|---|---|---|
|
QSA-20400 WHENEVER without WARNING or ERROR keyword |
The syntax of a WHENEVER command is incorrect. The WHENEVER command must specify either SQLERROR, ERROR, SQLWARNING, or WARNING. | If the script was automatically generated, contact Quest Software Support. |
|
QSA-20401 BEGIN TASK occurred outside of parallel block |
A BEGIN TASK command occurred outside of a parallel block. A task block is delimited by BEGIN_TASK and END_TASK. A task block can only occur inside a parallel block. | If the script was automatically generated, contact Quest Software Support. |
|
QSA-20402 END TASK without BEGIN TASK |
An END TASK command occurred outside a parallel block. Along with BEGIN_TASK, this command defines a task block. Task blocks can only occur inside a parallel block (delimited by BEGIN_PARALLEL and END_PARALLEL). They contain a group of SQL statements to be executed in parallel. | If the script was automatically generated, contact Quest Software Support. |
|
QSA-20403 END PARALLEL without BEGIN PARALLEL |
An END_PARALLEL command occurred without a corresponding BEGIN_PARALLEL command. Together, the two commands define a parallel block, used to support parallel script execution. | If the script was automatically generated, contact Quest Software Support. |
|
QSA-20404 Too many tasks |
The number of tasks within a parallel block exceeds the maximum allowed. The limit is 400 tasks. | Modify the script so that there are no more than 400 tasks within a parallel block. If you require more than 400 tasks, contact Quest Software Support. |
|
QSA-20405 Parallel factor is out of range |
The number of parallel operations specified is outside the range allowed. The range is from 1 to 20 inclusive. | Modify script options so that the number of parallel operations specified is from 1 to 20. Then regenerate the script. If you require more than 20 parallel operations, contact Quest Software Support. |
|
QSA-20406 Internal error in task engine |
This error should not occur under normal circumstances. | Contact Quest Software Support. |
|
QSA-20407 END_COPY command without BEGIN_COPY |
The END_COPY command occurred without the BEGIN_COPY command. | If the script was automatically generated, contact Quest Software Support. |
|
QSA-20408 Invalid parameter name |
The SET_PARAMETER() function was called with an invalid parameter name. | Correct the script with a valid parameter name. |
|
QSA-20409 Invalid parameter value |
The SET_PARAMETER() function was called with an invalid value for a parameter. | Correct the script with a valid parameter value. |
|
QSA-20411 Statement numbering is incorrect |
The script has been stored improperly. | Generate and store a replacement script (with the same options, if possible) under a different name. If the new script results in the same error, contact Quest Software Support. |
|
QSA-20412 Script terminates inside task block |
QSA detected that a script ended prematurely inside a BEGIN_TASK/END_TASK block. | Generate and store a replacement script (with the same options, if possible) under a different name. If the new script results in the same error, contact Quest Software Support. |
|
QSA-20413 Script terminates inside parallel block |
QSA detected that a script ended prematurely inside a BEGIN_PARALLEL / END_PARALLEL block. |
Generate and store a replacement script (with the same options if possible) under a different name. If the new script results in the same error, contact Quest Software Support. |
| Error | Cause | Action |
|---|---|---|
|
QSA-20500 Script/Engine version incompatible |
An attempt was made to run a script that is not compatible with the version of QSA currently installed. This error occurs for scripts that were generated for a version of QSA that is not compatible with the current version. |
Regenerate the script. |
|
QSA-20501 Approval type not recognized |
An invalid approval type was specified for the switch from original table to reorganized table. | Contact Quest Software Support. |
|
QSA-20502 Target completion date/time expired |
A script did not reach the COMPLETE_POSTING stage of live reorganization within the time window specified for the switch from original table to reorganized table. | Reschedule the script and adjust times for the window, if necessary. Allow enough time between the start of execution and the end of the window for the table to be reorganized, for indexes to be created, and for all live updates to be posted to the reorganized table. These tasks could take several hours for a large table. |
|
QSA-20504 Table contains large data type without a primary key or non-nullable unique key |
This error may occur during live reorganizations of tables that do not have a PRIMARY KEY or non-nullable UNIQUE index, but contain a BFILE or NESTED TABLE datatype. A PRIMARY KEY or unique index is required as the posting index. The error should not occur for tables with a LONG, LONG RAW, CLOB, BLOB, REF, VARRAY, OBJECT, or XMLTYPE datatype. All of these datatypes are supported and can be reorganized with a ROWID posting index or the “all columns” posting method. See Posting Indexes for more information. |
Contact Quest Software Support. |
|
QSA-20506 Malformed script |
This error occurs when a live reorganization script is missing an LW_START_REORG command, a BEGIN_COPY command, or an END_COPY command. Missing commands can result from problems in script generation or script edits by users. This error also occurs when you try to run a live reorganization script generated with a pre-5.6 version of Space Manager. |
Contact Quest Software Support. |
|
QSA-20522 Trigger lock is not possible |
QSA could not place a trigger lock on a table undergoing a live reorganization. The problem can occur when a table has multiple triggers for the same event or when there is a conflict with other activity against the database. | Check the table definition for multiple triggers for the same event. If these do not exist, re-run the reorganization script. If the problem occurs again, contact Quest Software Support. |
|
QSA-20524 Cannot reorg while snapshot replication is enabled |
A live reorganization should not be performed for a table which is being replicated via snapshot replication. | If you want to perform a live reorganization for a table with snapshot replication, please contact Quest Software Support. |
|
QSA-20525 Cannot reorg table with security policies enabled |
Security policies interfere with the T-locks (trigger locks) used during the switch stage of a live reorganization and can prevent the switch from original table to reorganized copy table from completing. | If you want to perform a live reorganization for a table with security policies, please contact Quest Software Support. |
|
QSA-20527 Possibly unsafe to reorg this table |
An attempt was made to reorganize a table owned by SYS or SYSTEM, or a table whose name starts with QUEST_. Generally, these tables do not need to be reorganized. Reorganizing them might result in unpredictable behavior by Oracle or QSA. | Determine whether the table truly needs to be reorganized. If it does, contact Quest Software Support for assistance in completing the reorganization. |
|
QSA-20531 Invalid script, no prior switch |
A SWITCH_COMPLETE command is missing from the live reorganization script. |
Regenerate the live reorganization script and run it. Do not delete any SWITCH_COMPLETE commands. If the problem occurs again, contact Quest Software Support. |
|
QSA-20532 Attempt to restart script failed |
An attempt to restart a script failed. Typically, this happens at the beginning of a restart. It can occur for any of the following reasons: a LiveReorg object is missing; QSA cannot find the script; the restart point is not valid; there is an inconsistency in the persistent storage data used by QSA; an object ID is different from what is expected. (An ID can be different if an object was reorganized with another script while the failed script was waiting for restart.) | Contact Quest Software Support. |
| Error | Cause | Action |
|---|---|---|
|
FC-20601 An underlying Oracle error occurred |
An Oracle error occurred. | Review Oracle's error message for the specific cause. Then take Oracle's recommended action and restart the reorganization script using the Restart function. |
|
FC-20602 An underlying SQL*Loader error occurred |
A SQL*Loader error occurred. | Review SQL*Loader's error message for the specific cause. Then take Oracle's recommended action and restart the reorganization script using the Restart function. |
|
FC-20603 An underlying OS error occurred |
An operating system error occurred. | Review the operating system error message. Then take the recommended action and restart the reorganization script using the Restart function. If no corrective action is recommended, write down the complete error message and contact Quest Software Support. |
|
FC-20605 Invalid function arguments |
Invalid function arguments were used. | Contact Quest Software Support. |
|
FC-20606 Out of memory |
The operating system is out of memory. | Reduce the number of running processes, increase operating system swap space, and/or increase ULIMIT resources. Then restart the script using the Restart function. |
|
FC-20607 Invalid parameter identifier |
An invalid identifier was used for a FastCopy parameter. | Contact Quest Software Support. |
|
FC-20608 Invalid parameter value |
An invalid value was entered for a FastCopy parameter. | Contact Quest Software Support. |
|
FC-20609 Functionality not yet implemented |
An attempt was made to use a QSA Server Agent function that has not been implemented. | Contact Quest Software Support. |
|
FC-20611 Write failure on stream |
The file system is full or a communication failure occurred during a data move. | Correct the file system error and/or assign additional OVERFLOW directories. Then restart the reorganization script using the Restart function. If the error persists, contact Quest Software Support. |
|
FC-20612 File not found |
The export file specified for reading during import of data was not found. | Contact Quest Software Support. |
|
FC-20613 Disk space is low |
The limit on the disk space reserved for FastCopy files in WORKDIR and OVERFLOW has been reached. | Assign additional OVERFLOW directories or decrease the value for the DISKSPACE_RESERVE parameter. The directories and DISKSPACE_RESERVE are specified with QSA Server Agent parameters. Restart the script using the Restart function. If the error persists, contact Quest Software Support. |
|
FC-20614 No export workdir found |
No WORKDIR directory was found. | Specify a directory for QSA’s WORKDIR parameter. |
|
FC-20615 Unexpected end of file |
An unexpected end of file was detected while reading an export file. | Contact Quest Software Support. |
|
FC-20616 Can't link direct export function |
The direct export function was not found. This error is usually due to an installation problem or a conflict in Oracle version support. For example, this error will occur if the Oracle DLL in the ORACLE_HOME/bin directory is not the DLL for the version of Oracle currently installed. This directory may contain the wrong DLL if Oracle has been upgraded. The DLL is not automatically updated during upgrades to some versions of Oracle. | Reinstall your application or contact Quest Software Support. If the ORACLE_HOME/bin directory contains the wrong Oracle DLL, copy the right DLL to that directory for the version of Oracle you are running FastCopy against. |
|
FC-20617 Table descriptions are incompatible |
Column count or column attributes do not match for the original table and copy table. | Make sure the table definitions are identical and retry. |
|
FC-20618 Table checksum comparison don't match |
Checksums do not match for the original table and copy table. | Contact Quest Software Support. |
|
FC-20619 Destination table must be empty |
The destination table is not empty. It must be empty for table insert mode. |
Contact Quest Software Support. |
|
FC-20622 No table objects found |
The tables specified for export were not found in the data dictionary. If partitions or subpartitions were specified, they have been found but contain no data. |
Make sure the owner and table names specified are correct. Contact Quest Software Support. |
|
FC-20623 Direct load row buffer overflow |
The direct load import row buffer exceeds the maximum size allowed. | Set QSA's IMPORT_METHOD parameter to CONVENTIONAL. Then restart the reorganization script using the Restart function. |
|
FC-20624 Direct load data conversion error |
A conversion error occurred during a direct load import. | Contact Quest Software Support. |
|
FC-20625 Direct load rows loaded different from direct export rows processed |
The SQL*Loader dropped row data. | Set QSA's IMPORT_METHOD parameter to CONVENTIONAL. Then restart the reorganization script using the Restart function. |
|
FC-20626 Direct load log file parsing error |
An error occurred during parsing of the SQL*Loader log file. Either the log file was not found or the log file is incomplete. | Set QSA's IMPORT_METHOD parameter to CONVENTIONAL. Then restart the reorganization script using the Restart function. |
|
FC-20627 Direct load SQL*Loader not running |
The SQL*Loader terminated prematurely. | Set QSA's IMPORT_METHOD parameter to CONVENTIONAL. Then restart the reorganization script using the Restart function. |
|
FC-20628 SQL*Loader terminated abnormally |
The SQL*Loader terminated with an error. | Set QSA's IMPORT_METHOD parameter to CONVENTIONAL. Then restart the reorganization script using the Restart function. |
|
FC-20629 Direct load unsupported data type |
A direct load was attempted for an unsupported datatype. |
Set QSA's IMPORT_METHOD parameter to CONVENTIONAL. Then restart the reorganization script using the Restart function. |
|
FC-20630 Direct load all null columns detected |
Rows containing all null columns were detected. SQL*Loader cannot insert these rows. | Set QSA's IMPORT_METHOD parameter to CONVENTIONAL. Then restart the reorganization script using the Restart function. |
|
FC-20632 Column ‘NAME’ datatype is not supported |
The current version of FastCopy does not support user-defined datatypes or the CLOB, BLOB, BFILE, CFILE, and MSLABEL datatypes. | Do not use FastCopy for unsupported types. |
|
FC-20633 Direct path export fail |
An Oracle bug causes direct path export to fail. | Contact Quest Software Support. |
|
FC-20636 Empty SQL select list |
An internal error occurred. | Contact Quest Software Support. |
|
FC-20642 FastCopy export file exists |
FastCopy has encountered an existing export file and will not overwrite it. The file may contain exported data from a table that was dropped during a previous reorganization that failed. | Contact Quest Software Support. |
Administration Functions
License Key
After you first install the Space Manager client and try to connect to a database, you are prompted to enter a license key. Once you enter a permanent key, you do not need to enter it again. It is preserved during upgrades. You only need to change or re-enter a license key when:
- Your trial key expires.
- You switch from a trial key to a permanent key.
- You change your licensing agreement with Quest Software.
- You uninstall and then reinstall the Space Manager client.
To update a license key
- Select Tools | Admin | License Key.
- Enter your permanent or trial license key.