# CHARACTER_SET_NAME=SPANISH_SPAIN.WE8MSWIN1252 / Copyright (c) 1991, 1996, 1997, 1998, 1999 by the Oracle Corporation. All rights reserved. / / / $Header: netius.msg 12-feb-99.11:25:06 smendiol Exp $ / / / NAME / netius.msg - NETwork Internal message file - U.S. english version / / / FUNCTION / Internal network error message file, American English version. / / / NOTES / Only internal errors are to be put into this file. External / messages are to put into netus.msg. / / This file, along with netus.msg, forms tnsus.msg. As a result, the / errors in this file may not overlap with the errors in that file. / Otherwise, errors will result when generating tnsus.msb. / / Message text should be limited to a maximum of 76 characters. / Messages containing embedded % directives should not overrun / the 76 character limit unless they signal unusual errors / which do not occur as part of user applications. For example, / startup errors and system-dependent errors can probably get / away with longer message text. / / / '/' at beginning-of-line for comments. / '//' at beginning-of-line for *Cause: and *Action: fields. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////// Please maintain this map ////////////////////// / / 00000 Not an error. // 00001 - 00500 NR (not reportable to OSN) - do not document / 00501 - 01000 NT (not reportable to OSN) - do not document / 01001 - 02500 NSG (not reportable to OSN) - do not document / 02501 - 03500 NA (not reportable to OSN) - do not document / 03501 - 03600 NSPING (not reportable to OSN) - NS ping utility / 03601 - 03700 NSUT (not reportable to OSN) - NS trace route utility / 04001 - 04200 NFP (not reportable to OSN) - do not document / 04201 - 04300 NU (not reportable to OSN) - do not document / . / . / / 12150 - 12285 See net12150.msg / 12500 - 12699 See net12500.msg /////////////////////////// Please maintain this map ////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / / / / OWNER / Network and Management Products - Server Technologies / / MODIFIED / smendiol 02/12/99 - Fixing type for TrcAsst Warning / skanjila 03/13/98 - Make translation changes for CMan in 805. / smendiol 01/22/98 - Adding NU error messages / tmlee 04/30/97 - executable name changes, new names: cmctl, cmgw, and / emalasky 04/15/97 - adding lsnrctl mesgs / pmitra 03/28/97 - CLB errors 2401-2500 / jgraham 03/21/97 - remove reference to CONFIG.ORA / rwessman 03/19/97 - Eliminated references to Secure Network Services. It / rwessman 03/16/97 - Fixed comment / rwessman 03/09/97 - Split from tnsus.msg / dhwu 10/24/96 - fix for 356374 / ygan 10/19/96 - Bug #358488: Modify message for 12500 / dlau 10/10/96 - Adding Connection Manager messages / dlau 10/07/96 - Add Connection Manager messages. / emalasky 09/30/96 - / emalasky 09/17/96 - / ygan 08/06/96 - Change message for set password for the listener / ygan 08/06/96 - Bug 350196 / mkanaley 02/19/92 Add NSG messages, remove 1040 / / sviavant 02/18/92 Creation / /////////////////////////////////////////////////////////////////////////// / 00000, 00000, "No es un error" // *Cause: Everything is working as it should. // *Action: Don't worry: Be happy. / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 00001 - 00500 NR errors / /////////////////////////////////////////////////////////////////////////// / / The range 00100 to 00200 should be reserved for the Network Routing / Gateway ConTroL program. The messages will include status messages / as well as error messages. / / Start with error messages first. / 00001, 00000, "INTCTL: error al acceder a la línea de comandos del terminal" // *Cause: Improper standard input connection from the terminal. // *Action: Normally not visible to the user. Start the INTCTL program again. // If error persists, contact Oracle Customer Support. / 00002, 00000, "INTCTL: error al arrancar el Intercambiador" // *Cause: The Interchange could not be started. // *Action: Check the Interchange configuration files (INTCHG.ORA, TNSNET.ORA // and TNSNAV.ORA) for errors and confirm that no other programs are using // the ADDRESS(es) specified. If error continues, turn on tracing in the // Interchange components and examine the trace files to determine the // cause of the problem. Be sure to turn tracing off when the problem has been // rectified. / 00003, 00000, "INTCTL: error al enviar la solicitud al Intercambiador" // *Cause: Improper command sent to the Interchange or the Interchange // is not responding. Not normally visible to the user. // *Action: Verify that the command sent to the Interchange is valid. // Also check that the Interchange is running by using the INTCTL STATUS // command. If necessary, start the Interchange using the INTCTL START // command. / 00004, 00000, "INTCTL: error al arrancar el Navegador" // *Cause: The Navigator could not be started. // *Action: Check to make sure that executables for the Navigator (navgatr) // are present in the ORACLE executable directory on // your platform. Check the configuration files TNSNET.ORA and TNSNAV.ORA // for errors. If error continues, turn on tracing in the Interchange // components and examine the trace files to determine the cause of the // problem. Be sure to turn tracing off when the problem has been // rectified. / 00005, 00000, "INTCTL: error al enviar la solicitud al Navegador" // *Cause: The Navigator is not responding. Either the Navigator is not // running or another process is responding. // *Action: Check that the Navigator is running by using the STATUS command // of the Interchange Control Utility. Verify that the correct addresses // are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration // files. / 00006, 00000, "INTCTL: la variable HOST no está definida" // *Cause: The HOST variable was not set. // *Action: Set the variable HOST properly and restart the INTCTL program. / 00007, 00000, "INTCTL: host desconocido" // *Cause: The pointer HOST is set to an unknown hostname. // *Action: Set the pointer HOST properly and restart INTCTL program. / 00008, 00000, "INTCTL: no se ha podido contactar con el Navegador destino" // *Cause: Connection could not be properly established to a Navigator. // This may be because the Navigator specified is not running or the Navigator // addresses are incorrect. // *Action: Check that the Navigator is running by using the STATUS // command of the Interchange Control Utility; if necessary, start the // Navigator using the START command of the Interchange Control Utility. // If it is running and the error persists, contact Oracle Customer // Support. / 00009, 00000, "INTCTL: no se ha podido contactar con el Connection Manager destino" // *Cause: Connection could not be properly established to a Connection // Manager. This may be because the Connection Manager (Interchange) // specified is not running or the Connection Manager addresses are incorrect. // *Action: Make sure the Connection Manager is running by using the STATUS // command of the Interchange Control Utility; if necessary, start the // Connection Manager using the START command of the Interchange Control // Utility. If it is running and the error persists, contact Oracle Customer // Support. / 00010, 00000, "Error al vaciar el contexto de NS" // *Cause: Internal NS error; connection may be lost. // *Action: Make sure the connection is properly established. If the // error persists, then contact Oracle Customer Support. / 00011, 00000, "INTCTL: error al arrancar el Connection Manager" // *Cause: The Connection Manager could not be started. // *Action: Assure that the executable can be found in the standard Oracle // executable area. Check the configuration file INTCHG.ORA for errors and // confirm that no other process is using the ADDRESS(es) for this // Connection Manager as specified in TNSNET.ORA. // Tracing can also be turned on in the Connection Manager and detailed // information about the reason for the error determined. Consult the // MultiProtocol Interchange Administrator's Guide and Chapter 2 of this // manual for how to turn on tracing. / 00012, 00000, "INTCTL: error al procesar la solicitud del Connection Manager" // *Cause: An improper command was sent to the Connection Manager or it is not // responding. Not normally visible to the user. // *Action: Verify that the correct addresses are listed in the // TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files. Also check // that the Connection Manager is running by using the STATUS command of // the Interchange Control Utility. If the error persists, contact // Oracle Customer Support. / 00013, 00000, "INTCTL: error al ejecutar el comando de desconexión de NS" // *Cause: Internal NS error. Error in closing down connections. // *Action: Make sure the networking protocol being used is properly // installed on the machine. If the error persists contact // Oracle Customer Support. / 00014, 00000, "INTCTL: error al abrir el canal de entrada del terminal" // *Cause: Could not open standard terminal input. Internal error. // *Action: Normally not visible to the user. Restart the INTCTL program. // If error persists, contact Oracle Customer Support. / 00015, 00000, "INTCTL: error al cerrar el canal de entrada del terminal" // *Cause: Could not close terminal input channel. Internal error. // *Action: Normally not visible to the user. Restart the INTCTL program. // If error persists, contact Oracle Customer Support. / 00016, 00000, "INTCTL: error al ejecutar el comando de envío de NS" // *Cause: Internal NS error. Connection may be lost. // *Action: If the error persists contact Oracle Customer Support. / 00017, 00000, "INTCTL: error al ejecutar el comando de recepción de NS" // *Cause: Internal NS error. Connection may be lost. // *Action: If the error persists contact Oracle Customer Support. / 00018, 00000, "INTCTL: TNS_ADMIN no definido" // *Cause: The TNS_ADMIN pointer is improperly set. // *Action: No action necessary; TNS_ADMIN need only be set if you want to // use a different network environment. / 00019, 00000, "INTCTL: error al inicializar la interfaz de lenguaje nacional" // *Cause: The message file could not be found. // *Action: Make sure that the ORACLE environment is set and that the message // file is in the correct place. / 00020, 00000, "INTCTL: falta NAVIGATOR_DATA en TNSNAV.ORA" // *Cause: TNSNAV.ORA does not contain the NAVIGATOR_DATA component. // *Action: Define the ADDRESS(es) for the Navigator, then restart the INTCTL // program. / 00021, 00000, "INTCTL: falta INTERCHANGE_DATA en INTCHG.ORA" // *Cause: INTCHG.ORA does not contain an INTERCHANGE_DATA component. // *Action: Define the correct data for the Connection Manager, then restart // the INTCTL program. / 00022, 00000, "INTCTL: falta CMANAGER_NAME en INTCHG.ORA" // *Cause: INTCHG.ORA does not contain a CMANAGER_NAME component. // *Action: Define the correct name for the CMANAGER_NAME, then restart // the INTCTL program. / 00023, 00000, "INTCTL: falta ADDRESS(es) en ficheros de configuración" // *Cause: Configuration files do not contain an ADDRESS/ADDRESS_LIST // component. // *Action: Define the Connection Manager ADDRESS(es) in the TNSNET.ORA // file and check the Navigator ADDRESS(es) in the TNSNAV.ORA file, // then restart the INTCTL program. / 00024, 00000, "INTCTL: No se ha podido contactar con el Navegador para obtener la dirección del Connection Manager" // *Cause: The Navigator is not running. // *Action: Verify that the Navigator is running by doing a status // request on the Navigator (use the Interchange Control Utility command // STATUS). If necessaary, start the Navigator using the Interchange // Control Utility. Verify that the network is properly configured; // if the error persists, contact Worldwide Customer Support. / 00025, 00000, "INTCTL: El entorno de ORACLE no está configurado correctamente" // *Cause: The ORACLE environment is incorrectly set up. // *Action: Refer to the Oracle operating system specific documentation for // your platform for information on how the ORACLE environment should be set. // Correct it and rerun INTCTL. Make sure the ORACLE environment includes // the correct directories. / 00026, 00000, "INTCTL: directorio TNS_ADMIN definido y en uso" // *Cause: The TNS_ADMIN environment variable is set properly. INTCTL will // use the TNS_ADMIN directory. This is only an informative message. If // you do not want it to be used, and want the default directory to be used // instead, then unset TNS_ADMIN and reexecute. // *Action: None. / 00027, 00000, "INTCTL: No se ha podido resolver el nombre/dirección del Navegador" // *Cause: The Navigator's name to address definition is missing. // *Action: Check TNSNAMES.ORA file and make sure to include a definition for // the name specified. / 00028, 00000, "INTCTL: No se ha podido resolver el nombre/dirección del Connection Manager" // *Cause: The Connection Manager's name does not have a definition that the // Navigator knows about, nor is the name/address available in the // TNSNAMES.ORA file. The name may also be incorrect in the INTCHG.ORA // file. // *Action: Verify that the Connection Manager's name is in the TNSNET.ORA // file read by the Navigator or in the TNSNAMES.ORA file. Be sure that // INTCHG.ORA is correct. / 00031, 00000, "INTCTL: error interno de NT" // *Cause: Problem interfacing to the protocol adapters installed. // *Action: Normally not visible to the user. Try starting INTCTL // again. If the error persists, check the product installation. If it is // correct, contact Oracle Customer Support. / 00032, 00000, "INTCTL: error interno de NS" // *Cause: Problem interfacing with TNS. // *Action: Normally not visible to the user. Try starting INTCTL // again. If the error persists, check the product installation. If it is // correct, contact Oracle Customer Support. / 00033, 00000, "INTCTL: error interno de NL" // *Cause: Problem with internal TNS module NL. // *Action: Normally not visible to the user. Try starting INTCTL // again. If the error persists, check the product installation. If it is // correct, contact Oracle Customer Support. / 00034, 00000, "INTCTL: error interno de NR" // *Cause: Problem with internal Interchange routines. // *Action: Normally not visible to the user. Try starting INTCTL // again. If the error persists, check the product installation. If it is // correct, contact Oracle Customer Support. / 00035, 00000, "INTCTL: error al crear el nombre de fichero completo" // *Cause: Problem while constructing the full path for a file name because // the path name to the file or the environment variables are // incorrect. Files looked up include TNSNAMES.ORA, TNSNAV.ORA, INTCHG.ORA // and the error files for the Navigator and Connection Manager. // *Action: Check that all environment variables are defined correctly // and that all configuration files exist in their correct places. / 00036, 00000, "INTCTL: error al leer los ficheros de errores del Navegador o del Connection Manager" // *Cause: Problem while reading from Navigator or Connection Manager error // files generated by the Navigator or Connection Manager when they fail // to start. // *Action: Check that a standard Network Error directory exists and that all // privileges on the directory are appropriate. / 00037, 00000, "INTCTL: error al abrir los ficheros de errores del Navegador o del Connection Manager" // *Cause: Failed to open Navigator or Connection Manager error files when // they have failed to start. // *Action: Check that a Network Error directory exists and that all // privileges on the directory are appropriate. / 00038, 00000, "INTCTL: cadena de caracteres del comando o de la dirección mal definida" // *Cause: An unacceptable string was encountered while attempting // to send a message to either the Navigator or Connection Manager. // The addresses provided for either the Navigator or Connection Manager // may be incorrectly constructed. // *Action: Check all address strings in configuration files (TNSNAMES.ORA, // TNSNAV.ORA or TNSNET.ORA) and assure that they are properly formed. // Regenerate the files, if possible. If // all is correct, please contact Worldwide Customer Support. / 00039, 00000, "INTCTL: error al originar un proceso" // *Cause: An error was encountered while spawning a process due to an // internal operating system dependent problem. Machine resources may be // limited. // *Action: Retry command. Check permissions on Interchange // executables and the current setting of the search path. If necessary, // terminate other applications to free up machine resources. If the error // persists, contact Oracle Customer Support. / 00040, 00000, "INTCTL: fallo al inicializar el contexto de rastreo. Continúa el proceso" // *Cause: Problem while opening specified trace file because of errors in // INTCHG.ORA or because the user has incorrect privileges, or the file does // not exist. // *Action: Check the privileges on the configuration files and ensure that // all of them exist in their proper locations. / 00041, 00000, "INTCTL: El Navegador ya se está ejecutando. Operación de arranque cancelada" // *Cause: There is a Navigator already running and listening on the same // addresses. // *Action: None; the Navigator is already running. / 00042, 00000, "INTCTL: El Connection Manager (CMANAGER) ya se está ejecutando. Operación de arranque cancelada" // *Cause: There is a Connection Manager already running and listening on // the same addresses. // *Action: None; the Connection Manager is already running. / 00043, 00000, "El Connection Manager tiene conexiones activas, ¿desea pararlo de todos modos (s/n)?" // *Cause: The CMANAGER that is being stopped has active connections going // through. This is the confirmation message. // *Action: Respond by pressing y or n. Answering y will cause the active // database connection to be dropped; this is not generally recommended. / 00044, 00000, "INTCTL: Es necesario un fichero INTCHG.ORA para contactar con el Connection Manager" // *Cause: There was an attempt to contact a default Connection Manager // (Interchange) where there was no INTCHG.ORA present in the correct // directory. // *Action: Create an INTCHG.ORA file. // Make sure it is placed in the correct directory and includes the correct // name for the Connection Manager you wish to contact. / 00045, 00000, "INTCTL: No se ha podido contactar con el Navegador en la dirección especificada" // *Cause: There was an attempt to contact a Navigator on a specific address // which is not responding. // *Action: Check the TNSNAV.ORA file for that address. Or check that the // Navigator is actually listening on that address. / 00046, 00000, "INTCTL: No se ha podido contactar con el Connection Manager en la dirección especificada" // *Cause: There was an attempt to contact a CMANAGER on a specific address // which is not responding. // *Action: Verify that the TNSNET.ORA file contains that address. Also check // that the CMANAGER is actually listening on that address by using the INTCTL // STATUS command. If necessary, start the Connection Manager using the INTCTL // START command. / 00060, 00000, "INTCTL: Comando incorrecto: en Intercambiadores remotos sólo puede usarse el comando STATUS" // *Cause: The user entered a command that does not exist, or the user // tried to make a request other than STATUS to a remote Interchange. // *Action: Check the MultiProtocol Interchange Administrator's Guide for // a list of INTCTL commands or type HELP for a list of valid commands. / 00061, 00000, "INTCTL: Comando incorrecto o error de sintaxis: debe especificar un nivel de rastreo" // *Cause: The user did not specify a trace level. // *Action: Specify a trace level and retry command. / 00062, 00000, "INTCTL: Comando incorrecto o error de sintaxis: para ayuda, escriba ayuda/h/?" // *Cause: The user entered an invalid command. // *Action: Check the MultiProtocol Interchange Administrator's Guide or type // HELP for a list of valid commands. / 00063, 00000, "INTCTL: Fallo al asignar memoria a los buffers" // *Cause: INTCTL was unable to allocate memory for internal buffers. // *Action: Check the amount of available memory on your machine to ensure // that there is enough memory to run this executable. If necessary, free up // memory by running fewer programs, then try again. / 00064, 00000, "INTCTL: No se ha podido encontrar CMANAGER_NAME en INTCHG.ORA" // *Cause: INTCTL was unable to find the CMANAGER_NAME parameter in INTCHG.ORA. // *Action: Check that the INTCHG.ORA file is properly constructed. / 00065, 00000, "INTCTL: No se puede ejecutar el comando remotamente" // *Cause: A command other than status and version has been attempted // remotely. // *Action: If you desire execute any command other than status and version, // you must run intctl on the interchange machine. / / The range 00070 to 00099 will be reserved for the help messages used by / INTCTL program / 00070, 00000, "sintaxis de INTCTL: [intctl] [argumento]\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00071, 00000, " donde es uno de los siguientes: \n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00072, 00000, " * start - arranca el nombre_proceso\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00073, 00000, " * stop/abort - finaliza el nombre_proceso\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00074, 00000, " * status - obtiene estadísticas del nombre_proceso\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00075, 00000, " NOTA: el usuario puede obtener información sobre el\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00076, 00000, " estado de un componente remoto especificando\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00077, 00000, " el nombre del componente en el campo de argumento\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00078, 00000, " * log_on - solicita a nombre_proceso la conexión\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00079, 00000, " * log_off - solicita a nombre_proceso la desconexión\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00080, 00000, " * force_log - solicita a nombre_proceso un volcado de su estado\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00081, 00000, " * trace_on - solicita a nombre_proceso que active el rastreo\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00082, 00000, " NOTA: el usuario DEBE especificar un nivel de rastreo\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00083, 00000, " (USER o ADMIN) en el campo Argumento\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00084, 00000, " * trace_off - solicita a nombre_proceso que desactive el rastreo\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00085, 00000, " * reread - solicita a nombre_proceso que vuelva a leer los ficheros de parámetros\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00086, 00000, " * reload - solicita al Navigator que vuelva a cargar TNSNET.ORA\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00087, 00000, " * version - solicita a nombre_proceso que muestre su número de versión\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00088, 00000, " * exit - sale del controlador Interchange\n\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00089, 00000, " nombre_proceso es Intercambiador, Connection Manager (CMANAGER) o Navegador\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00090, 00000, " * Interchange - llama al Intercambiador\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00091, 00000, " * Navigator (o navgatr) - llama sólo al Navegador\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00092, 00000, " * CMANAGER (o intlsnr) - llama sólo al Connection Manager\n\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00093, 00000, " el argumento sólo se proporciona a status o trace_on\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00094, 00000, " * to status - el argumento es considerado el nombre_proceso remoto\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / 00095, 00000, " * to trace_on - el argumento es considerado el nivel de rastreo\n\n" // *Cause: Help message displayed by INTCTL. // *Action: None. / / / / The range 00100 to 00400 should be reserved for the Multiprotocol Interchange / error messages and user visible messages / / Error messages for Interchange start at 100 / User visible messages start at 200 / 00100, 00000, "No se puede asignar memoria" // *Cause: Out of memory on the machine. // *Action: Add more memory or run fewer processes. / 00101, 00000, "Error de operación del fichero" // *Cause: Error in accessing reading or writing a particular file. // *Action: Check existence of or operating system access to the log and trace // file locations. / 00102, 00000, "Error de operación del enlace palabra clave-valor" // *Cause: Not normally visible to the user. May indicate a shortage of memory. // *Action: If error persists contact Oracle Customer Support. / 00103, 00000, "Error de carga del fichero de parámetros" // *Cause: Parameter file process failed. // *Action: Check to make sure that all parameter files necessary for the // Interchange are present (TNSNAV.ORA, TNSNET.ORA and INTCHG.ORA). // If these files are present and properly configured, turn on tracing and // repeat the operation. Turn off tracing when the trace is complete. Look // in the trace file for errors in the parameter loading process. // If error persists contact Oracle Customer Support. / 00104, 00000, "Error de apertura/acceso del flujo de datos" // *Cause: Unable to open or access data stream for either log or trace files // for the Interchange. // *Action: Check read/write permissions on Oracle files and directories. / 00105, 00000, "No se ha podido inicializar el rastreo" // *Cause: The INTCHG.ORA file is improperly configured. Verify the trace // parameters specified. // *Action: If error persists contact Oracle Customer Support. / 00106, 00000, "Fallo en la apertura del fichero log" // *Cause: Unable to access or obtain write permission to create log file. // *Action: Check existence of or access to log file directory. / 00107, 00000, "No se pueden inicializar datos globales de TNS" // *Cause: Not normally visible to the user. // *Action: If error persists contact Oracle Customer Support. / 00108, 00000, "TNS_ADMIN no definido" // *Cause: TNS_ADMIN pointer is not set. // *Action: Set the TNS_ADMIN pointer before running application / 00109, 00000, "No se ha podido imprimir el mensaje: memoria insuficiente" // *Cause: Printing of message failed due to lack of memory. Not normally // visible to user. // *Action: Increase the resources on your machine. If error persists contact // Oracle Customer Support. / 00110, 00000, "No se ha podido inicializar la red desde el fichero TNSNET.ORA" // *Cause: Poorly formed network information in network file. // *Action: Fix network configuration data to assure that at least one // Interchange is defined in TNSNET.ORA. / 00111, 00000, "No se han podido obtener los datos de configuración del fichero" // *Cause: Poorly formed configuration information in network files TNSNET.ORA // or TNSNAV.ORA. // *Action: Check TNSNET.ORA and TNSNAV.ORA and confirm that they are correct. / 00112, 00000, "No se ha podido encontrar el nombre del fichero de configuración" // *Cause: Name specified for configuration file was incorrect. // *Action: Check for presence of the configuration file. / 00113, 00000, "Fallo al abrir el fichero log de errores" // *Cause: Could not open log file during startup of Navigator or // Connection Manager due to read or write permission problems or non-existent // error directory. // *Action: Create the standard error directory or assure that if one // is present the Interchange executables can write to it. / 00114, 00000, "Error interno - no se ha efectuado la asignación de direcciones" // *Cause: Internal error. Should not normally occur. // *Action: Contact Oracle Customer Support. / 00115, 00000, "No se han podido asignar buffers globales de impulsores" // *Cause: Not enough memory to allocate pump buffers. // *Action: Decrease the number of PUMP_BUFFERS in INTCHG.ORA. / 00116, 00000, "Fallo del impulsor durante la conexión inicial" // *Cause: Error in assigning connection to a new pump. This error may be // caused by insufficient machine resources. // *Action: Attempt the connection again. The pump should recover from such // a failure. If machine resources appear to be the problem, add more resources // or shut down some active applications. If problem persists, contact // Oracle Customer Support. / 00117, 00000, "Error interno - No se han transmitido datos a través del impulsor" // *Cause: Internal error. Data expected has not arrived yet. // *Action: If error persists, contact Oracle Customer Support. / 00119, 00000, "Falta PUMP_CONNECTIONS en INTCHG.ORA" // *Cause: No PUMP_CONNECTIONS parameter specified in INTCHG.ORA. // *Action: Add PUMP_CONNECTIONS parameter to INTCHG.ORA. / 00120, 00000, "Falta PUMPS en INTCHG.ORA" // *Cause: No PUMPS parameter specified. // *Action: Add an appropriate number of PUMPS to INTCHG.ORA. / 00121, 00000, "Falta CMANAGER_NAME en INTCHG.ORA" // *Cause: No CMANAGER_NAME parameter specified. // *Action: Define the CMANAGER_NAME parameter in INTCHG.ORA; it must // match the CMANAGER_NAME parameter used in TNSNET.ORA for that // Interchange. / 00122, 00000, "Falta ADDRESS(es) en el fichero TNSNET.ORA" // *Cause: No ADDRESS or ADDRESS_LIST parameter specified in TNSNET.ORA. // *Action: Define a valid set of ADDRESSes for the Connection Manager in // the TNSNET.ORA file. / 00123, 00000, "No se puede realizar una recepción en la dirección (ADDRESS(es)) configurada" // *Cause: Another process is already listening on this address or the // ADDRESS is incorrectly defined. // *Action: Check the ADDRESS(es) defined in TNSNET.ORA (for the Connection // Manager) for errors. Verify that another program is not using them. / 00124, 00000, "Error interno - No se puede crear una dirección vacía" // *Cause: - Internal error. Should not normally occur. // *Action: If problem persists contact Oracle Customer Support. / 00125, 00000, "No se ha podido obtener el número de Intercambiadores en TNSNET.ORA" // *Cause: Error in the TNSNET.ORA file. // *Action: Check the contents of TNSNET.ORA and eliminate errors. Regenerate // the configuration files. / 00126, 00000, "Falta el nombre y la dirección del Connection Manager en TNSNET.ORA" // *Cause: The Interchange name specified in INTCHG.ORA is not defined in // the TNSNET.ORA file. // *Action: Define one Connection Manager name and set of addresses for // each Interchange in the network. Regenerate the configuration files. / 00127, 00000, "Falta el nombre del Connection Manager en TNSNET.ORA" // *Cause: One or more Connection Manager names are missing. // *Action: Ensure that each Connection Manager name is defined in // TNSNET.ORA. Regenerate TNSNET.ORA. / 00128, 00000, "Falta COMMUNITY en TNSNET.ORA" // *Cause: One or more ADDRESSes does not have a COMMUNITY assigned. // *Action: Ensure that all addresses have a COMMUNITY defined in TNSNET.ORA. / 00129, 00000, "Error interno - Fallo al crear una nueva comunidad" // *Cause: Internal Error. Should not normally occur. There may be a // resource limitation problem on the machine. // *Action: Stop and restart Interchange. If possible, make more memory // available on the machine. If problem persists, contact Oracle // Customer Support. / 00130, 00000, "No se ha podido crear la dirección interna del Intercambiador" // *Cause: There is an error in one of the addresses listed in TNSNET.ORA. // *Action: Check the file for errors in defining Interchanges. / 00131, 00000, "Falta COMMUNITY en COMMUNITY_COST_LIST en TNSNET.ORA" // *Cause: A COMMUNITY keyword-value pair is missing within the // COMMUNITY_COST_LIST in TNSNET.ORA. // *Action: Define the communities with a COMMUNITY name and associated COST // in COMMUNITY_COST_LIST. / 00132, 00000, "El valor de COST debe ser un número entero mayor que 0" // *Cause: A community has been defined in TNSNET.ORA with a COST of 0. // *Action: Assign an alternate value that is greater than 0. / 00133, 00000, "Falta el campo LOCAL_COMMUNITIES en TNSNAV.ORA" // *Cause: Improperly configured TNSNAV.ORA file. // *Action: Define the LOCAL_COMMUNITIES fields correctly in TNSNAV.ORA. / 00134, 00000, "Falta el componente COMMUNITY en las direcciones para el Navegador en TNSNAV.ORA" // *Cause: The addresses specified for the Navigator have no COMMUNITY name. // *Action: Ensure that all addresses in the NAVIGATOR_ADDRESSES field have // a COMMUNITY entry in the TNSNAV.ORA file. / 00135, 00000, "Falta el fichero de mensajes de error de TNS" // *Cause: No error message file present. // *Action: Ensure that the ORACLE environment is correctly set for your // platform and that there is a message directory that contains the correct // error message file. / 00136, 00000, "No se ha registrado el producto/utilidad para el mensaje de error de TNS" // *Cause: Error message file error. // *Action: Ensure that the ORACLE environment is correctly set for your // platform and that there is a message directory that contains the correct // error message file. / 00137, 00000, "No se ha podido obtener la entrada del fichero de mensajes de error de TNS" // *Cause: No TNS error message file present. // *Action: Ensure that the ORACLE environment is correctly set for your // platform and that there is a message directory that contains the correct // error message file. / 00138, 00000, "No se ha podido encontrar el directorio de ejecutables de ORACLE" // *Cause: The ORACLE environment is not correctly set. // *Action: Ensure that the ORACLE environment is correctly set and the // error messages file is in the correct place. / 00139, 00000, "Error Interno - Los datos enviados desde el listener del Intercambiador están mal definidos" // *Cause: Internal error in Interchange. // *Action: Check that you are using compatible components of the Interchange // product, using the INTCTL VERSION command. If problem persists call // Oracle Customer Support. / 00140, 00000, "El Intercambiador especificado no se ha encontrado en las tablas de la red" // *Cause: Could not find the Interchange specified in a control request. // *Action: Check that the Interchange specified is indeed in TNSNET.ORA. / 00141, 00000, "No se ha podido obtener información sobre el flujo de ficheros" // *Cause: Error in the file stream package. // *Action: None. / 00142, 00000, "La comunidad no coincide en TNSNAV.ORA" // *Cause: The communities in the LOCAL_COMMUNITIES entry in TNSNAV.ORA do // not correspond with all the communities in the NAVIGATOR_ADDRESSES // entry. // *Action: Assure that all communities in the NAVIGATOR_ADDRESSES correspond // to those in the LOCAL_COMMUNITIES component. / 00143, 00000, "Entrada PREFERRED_CMANAGERS incorrecta en TNSNAV.ORA" // *Cause: PREFERRED_CMANAGERS entry in the TNSNAV.ORA used by the Connection // Manager. There should only be a PREFERRED_NAVIGATORS entry in the // TNSNAV.ORA on an Interchange. // *Action: Remove the PREFERRED_CMANAGERS entry from TNSNAV.ORA and assure // that either no PREFERRED_NAVIGATORS entry is present or that it // is correct. / 00144, 00000, "El valor de PUMP_CONNECTIONS en INTCHG.ORA es demasiado grande." // *Cause: The number of PUMP_CONNECTIONS specified in INTCHG.ORA is too large // to be supported on this platform. // *Action: Consult the Oracle operating system specific manual for the maximum // value for the number of PUMP_CONNECTIONS. / 00145, 00000, "El valor PUMPS en INTCHG.ORA es demasiado grande" // *Cause: The number of PUMPS specified in INTCHG.ORA is too large // to be supported on this platform. // *Action: Consult the Oracle operating system specific manual for the // maximum value for the number of PUMPS. / 00146, 00000, "Error interno-- Vuelva a intentar solicitar los datos dentro del impulsor" // *Cause: The data space provided in order to receive data from the pump is // to small. // *Action: Operation must be retried with a larger buffer. / 00147, 00000, "Fallo al arrancar un impulsor predefinido" // *Cause: The Connection Manager was unable to start a pump during startup. // *Action: Check all configuration parameters and assure that they are // correct. Turn on tracing to determine the area that the failure ocurred in. / / User Visible messages, starting at 200 / Log and status messages. / 00200, 00000, "No se puede ejecutar nsanswer en context\nresult=%s\n" // *Cause: Requester of service may have aborted or options negotiation failed. // *Action: Try making the connection again. If the problem persists call // Oracle Customer Support. / 00201, 00000, "No se pueden leer datos de conexión de respuesta :%s:\n" // *Cause: Improperly formed connect data sent to the Interchange listener. // *Action: If problem persists, check the application using the // Interchange (it may be closing down or crashing). Call Oracle Customer // Support if the problem cannot be located. / 00202, 00000, "No se ha podido redirigir la llamada: \nOriginalmente a %s\n\t Redirigida a %s\n" // *Cause: Internal - error could not redirect call to a pump or other // Interchange listener. The cause may be insufficient network or machine // resources. // *Action: Add resources or close some running applications in order to // free up resources. If error persists, call Oracle Customer Support. / 00203, 00000, "No se puede iniciar el rastreo en intlsnr\n" // *Cause: Failure in setting up tracing for Interchange listener. // *Action: Check file permissions in Network trace directory also check // to make sure that if trace file names and directories are specified in // INTCHG.ORA, they are correct. / 00204, 00000, "Rastreo iniciado en intlsnr\n" // *Cause: Internal message- Successfully started tracing information. // *Action: None. / 00205, 00000, "Desactivación de rastreo en intlsnr\n" // *Cause: Internal message - Turned off tracing in the Interchange listener. // *Action: None / 00206, 00000, "\n\nInformación de estado para el Intercambiador %s:\n" // *Cause: Message sent back by Interchange as header for status request. // *Action: None / 00207, 00000, "\tTiempo de actividad : %lu días %lu hr. %lu min. %lu seg.\n" // *Cause: Part of status request. // *Action: None / 00208, 00000, "\tRegistro : %s\n" // *Cause: Part of status request. // *Action: None / 00209, 00000, "\tRastreo : %s\n" // *Cause: Part of status request Interchange. // *Action: None / 00210, 00000, "\tTotal de impulsores disponibles: %u\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00211, 00000, "\tTotal de impulsores activos : %u\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00212, 00000, "\tTotal de impulsores arrancados: %u\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00213, 00000, "\tConexiones disponibles : %lu\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00214, 00000, "\tTotal de conexiones en uso : %lu\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00215, 00000, "\tTotal de conexiones correctas : %lu\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00216, 00000, "\tTotal de conexiones fallidas : %lu\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00217, 00000, "\tTotal de bytes de datos : %lu\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00218, 00000, "\tBytes/seg. actuales : %.2f\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00219, 00000, "\tEstrategia del impulsor : %s\n" // *Cause: Part of status request. // *Action: None / 00220, 00000, "\tImpulsores averiados \n\t--------------------\n" // *Cause: Part of status request. // *Action: None / 00221, 00000, "\tImpulsor Conexiones Datos totales Bytes/Segundo\n" // *Cause: Part of status request. // *Action: None / 00222, 00000, "\t-------------------------------------------------------------------\n" // *Cause: Part of status request. // *Action: None / 00223, 00000, "\t%5u%12u%26lu%22.2f\n" // *Cause: Part of status request. // *Action: None / 00224, 00000, "No hay más conexiones disponibles\n" // *Cause: More connections were made to the Interchange than are configured // in INTCHG.ORA. // *Action: Wait until the Interchange is not as busy or change the number of // connections allowed in INTCHG.ORA and restart the Interchange. / 00225, 00000, "No se ha podido transmitir la conexión a un impulsor\n" // *Cause: Unable to start a pump because either the executable cannot be // found or too many processes aare currently running on a particular machine. // *Action: Reduce the number of processes on the machine or increase the // resources on the machine. / 00226, 00000, "No se ha podido contactar con el impulsor %d para enviar el mensaje %s\n" // *Cause: Could not call a particular pump. // *Action: None, but if the problem persists call Oracle Customer Support. / 00227, 00000, "No se puede contactar con el impulsor; el Connection Manager lo ha declarado inoperativo\n" // *Cause: A pump became an orphaned process. A protocol adapter is not // working properly or machine network resources are being over used. // *Action: This error is not immediately fatal; the orphaned pump may // continue to function. Restart the Interchange when convenient. If the // problem persists, call Oracle Customer Support. / 00228, 00000, "No se han podido encontrar los datos del impulsor\n" // *Cause: Internal problem with data passed back from pump. // *Action: None. / 00229, 00000, "Error en la llamada: no se ha podido entregar el mensaje\n:%s:\n%s\n%s\n%s\n" // *Cause: Destination for call is unavailable. // *Action: None. / 00230, 00000, "No se puede arrancar un nuevo proceso del impulsor:\n%s\n%s\nErrores del adaptador de protocolo:%u" // *Cause: Unable to create a new process; possibly there are too many // processes on the machine. // *Action: Free machine resources by exiting other applications on the // Interchange machine. If the problem continues you may need more memory // on the machine. If you believe there are sufficient resources on the // machine but the problem persists, contact Oracle Customer Support. / 00231, 00000, "El impulsor está activo\n" // *Cause: Pump log message sent to Interchange listener. // *Action: None. / 00232, 00000, "No se ha podido configurar la conexión\n" // *Cause: Error log message sent from pump to indicate failure in initiating // connection because of errors in the call string: network problem or // resource limitations. // *Action: None. / 00233, 00000, "El Intercambiador no ha podido contactar con el destino con errores:\n%s\n%s\n%s\n" // *Cause: Pump call to destination failed. // *Action: Check destination. / 00234, 00000, "Datos de conexión para llamada fallida:\nCALL DATA =\n%s\nRECEIVE DATA = :%s:\n" // *Cause: Connect data supplied for error 00233. // *Action: None / 00235, 00000, "Conexión abortada:\nErrores del adaptador de protocolo:\n%s;%u,%u\n%s;%u,%u\n" // *Cause: Pump aborting connection because connection has been up too long, // or some other network error on the connection. // *Action: None. / 00236, 00000, "Fallo al inicializar el rastreo\n" // *Cause: Pump failed to initialize tracing. // *Action: Check that INTCHG.ORA is properly configured. / 00237, 00000, "Fallo al rechazar la conexión\n" // *Cause: Connection may have aborted before error took place in Pump. // *Action: None. / 00238, 00000, "Impulsor %d @: %s: " // *Cause: Prepended message to all pump log messages. // *Action: None. / 00239, 00000, "El Connection Manager se ha parado" // *Cause: Message sent back to control program from Interchange. // *Action: None. / 00240, 00000, "Connection Manager: El registro está ahora activado (ON)" // *Cause: Message sent back to control program from Interchange. // *Action: None. / 00241, 00000, "Connection Manager: El registro está ahora desactivado (OFF)" // *Cause: Message sent back to control program from Interchange. // *Action: None. / 00242, 00000, "Connection Manager: El rastreo está ahora activado (ON)" // *Cause: Message sent back to control program from Interchange. // *Action: None. / 00243, 00000, "Connection Manager: El rastreo está ahora desactivado (OFF)" // *Cause: Message sent back to control program from Interchange. // *Action: None. / 00244, 00000, "Connection Manager: La solicitud ha fallado" // *Cause: Message sent back to control program from Interchange. // *Action: None. / 00245, 00000, "Connection Manager: no se ha podido abrir el fichero log" // *Cause: Message sent back to control program from Interchange. // *Action: None. / 00246, 00000, "Connection Manager: no se ha podido iniciar el rastreo" // *Cause: Message sent back to control program from Interchange. // *Action: None. / 00247, 00000, "No se puede asignar memoria para los datos de configuración del fichero TNSNET.ORA" // *Cause: Navigator failed to allocate enough memory for TNSNET.ORA // configuration file. // *Action: Increase machine resources available for running the // Interchange or remove some other running applications from the machine. / 00248, 00000, "No se ha podido obtener información del fichero :%s:\nSaliendo con error NR:%d\n" // *Cause: TNSNAV.ORA poorly configured or addresses provided are already being // used by another application. // *Action: Check the syntax of the TNSNAV.ORA file; if necessary, assign // new addresses. / 00249, 00000, "No se pueden leer los datos de configuración de la red del fichero %s\ncon error:\n %s\n" // *Cause: Network configuration file TNSNET.ORA is missing or poorly // configured. // *Action: Check to make sure that TNSNET.ORA is properly configured. / 00250, 00000, "El Navegador se ha arrancado\n" // *Cause: Message to log file on Navigator startup. // *Action: None. / 00251, 00000, "Fallo en nstest: \n" // *Cause: NS test operation failed due to internal error. // *Action: If the problem persists there may be a network problem or // resource limitations on the machine. If these do not seem to be causing // the problem, call Oracle Customer Support. / 00252, 00000, "No se ha podido gestionar la solicitud de ruta:\n%s\n" // *Cause: Command requested did not exist. // *Action: None. / 00253, 00000, "Error al leer los datos de configuración de la red del fichero %s\n con error\n%s\n" // *Cause: TNSNET.ORA is poorly configured or nonexistent. // *Action: Check to make sure that TNSNET.ORA is properly configured. / 00254, 00000, "El Navegador se ha parado\n" // *Cause: Message sent to Interchange control program by Navigator confirming // it has been stopped. // *Action: None. / 00255, 00000, "Cerrando el log, parando el Navegador\n" // *Cause: Log message when Navigator is stopped. // *Action: None. / 00256, 00000, "Estado del Navegador:\n" // *Cause: Navigator status message component // *Action: None. / 00257, 00000, "\tNúmero de Solicitudes Correctas: %lu\n" // *Cause: Navigator status message component // *Action: None. / 00258, 00000, "\tNúmero de Solicitudes Fallidas : %lu\n" // *Cause: Navigator status message component // *Action: None. / 00259, 00000, "\tLista de Intercambiadores Desactivados:\n\t\n" // *Cause: Navigator status message component // *Action: None. / 00260, 00000, "\t-----------------------------------------------------------------------------\n" // *Cause: Navigator status message component // *Action: None. / 00261, 00000, "\tNombre Intercambiador Enlace Comunidad Tiempo Inactividad Restante (segs) \n" // *Cause: Navigator status message component // *Action: None. / 00262, 00000, "%20s%20s%30d\n" // *Cause: Navigator status message component // *Action: None. / 00263, 00000, "Navegador: La solicitud ha fallado" // *Cause: Response from Navigator when a particular request failed. // *Action: None. / 00264, 00000, "Navegador: Fallo al intentar volver a cargar los datos de configuración" // *Cause: Message sent to the Interchange control program when reload of // network configuration failed. TNSNET.ORA Poorly configured or // missing. // *Action: None. / 00265, 00000, "Navegador: Datos de configuración de red cargados de nuevo" // *Cause: Message sent to Interchange control program when reload of network // is successful. // *Action: None. / 00266, 00000, "Navegador: Solicitud desconocida" // *Cause: Request was made to Navigator that it knows nothing about. // *Action: None. / 00267, 00000, "Navegador: Error interno" // *Cause: Generated when a request was made to the Navigator it knows nothing // about. // *Action: None. / 00268, 00000, "Activado (ON)" // *Cause: On component of message. // *Action: None. / 00269, 00000, "Desactivado (OFF)" // *Cause: Off component of message. // *Action: None. / 00270, 00000, "%s: Error de terminal\n%s\n" // *Cause: Message put out in error file of executable when it fails to start. // *Action: None. / 00271, 00000, "Connection Manager" // *Cause: Name of the Connection Manager. // *Action: None. / 00272, 00000, "Navegador" // *Cause: Name for the Navigator. // *Action: None. / 00273, 00000, "Navegador: El registro está ahora activado (ON)" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00274, 00000, "Navegador: El registro está ahora desactivado (OFF)" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00275, 00000, "Navegador: El rastreo está ahora activado (ON)" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00276, 00000, "Navegador: El rastreo está ahora desactivado (OFF)" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00277, 00000, "Navegador: La solicitud ha fallado" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00278, 00000, "Navegador: Fallo al abrir el fichero log" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00279, 00000, "Navegador: Fallo al iniciar el rastreo" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00280, 00000, "\tMedia máxima de bytes/seg. : %.2f\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00281, 00000, "Connection Manager: salida forzada del log\n" // *Cause: Message sent back to control program from Connection Manager. // *Action: None. / 00282, 00000, "Connection Manager: no se ha podido forzar el log; el registro está desactivado\n" // *Cause: Message sent back to control program from Connection Manager. // *Action: None. / 00283, 00000, "\nEscucha en las siguientes direcciones TNS:\n\n" // *Cause: Message sent back to control program from Connection Manager. // *Action: None. / 00284, 00000, "\tMedia máxima inm. de bytes/seg. : %.2f\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00285, 00000, "\tTiempo medio de conexión (seg.) : %.2f\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00286, 00000, "\tTiempo máximo de conexión (seg.): %.2f\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00287, 00000, "\tTiempo mínimo de conexión (seg.): %.2f\n" // *Cause: Part of status request for Connection Manager. // *Action: None / 00288, 00000, "Navegador: No se ha podido desactivar el Intercambiador" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00289, 00000, "Navegador: Intercambiador desactivado" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00290, 00000, "Navegador: No se ha podido activar el Intercambiador" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00291, 00000, "Navegador: Intercambiador activado" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00292, 00000, "\tNombre del fichero log :\n\t\t%s\n" // *Cause: Message sent back to control program showing log file name // *Action: None. / 00293, 00000, "\tNombre del fichero de rastreo :\n\t\t%s\n" // *Cause: Message sent back to control program showing trace file name // *Action: None. / 00294, 00000, "Connection Manager: seguridad activada, no puede parar (STOP) el Intercambiador\n" // *Cause: Message sent back to control program indicating that the connection // manager is secure. // *Action: None. / 00295, 00000, "Navegador: seguridad activada, no puede parar (STOP) el Navegador\n" // *Cause: Message sent back to control program indicating that the Navigator // is secure. // *Action: None. / 00296, 00000, "\tParable : %s\n" // *Cause: Message sent back to control program indicating whether program // can be stopped. // *Action: None. / 00297, 00000, "\tNivel de registro : %s\n" // *Cause: Message sent back to control program indicating whether program // can be stopped. // *Action: None. / 00298, 00000, "Solicitud al Navegador:\n%s\n" // *Cause: Log entry for request to Navigator. // *Action: None. / 00299, 00000, "Respuesta del Navegador:\n%s\n" // *Cause: Log entry for request to Navigator. // *Action: None. / 00300, 00000, "***Desactivando el Intercambiador : %s\n" // *Cause: Log entry for disabling a particular Interchange. // *Action: None. / 00301, 00000, "***Activando el Intercambiador : %s\n" // *Cause: Log entry for disabling a particular Interchange. // *Action: None. / 00302, 00000, "Connection Manager: Solicitud desconocida" // *Cause: Request sent by Interchange control program is unknown. // *Action: None. / 00303, 00000, "Connection Manager: Volver a leer los datos de parámetros" // *Cause: Request sent by control manager to control programming indicating // that parameter data was read. // *Action: None. / 00304, 00000, "Información de estado para el Connection Manager:\n" // *Cause: Message sent back by Interchange as header for status request. // *Action: None / 00305, 00000, "El Navegador ha localizado un nivel de rastreo desconocido/incorrecto\n" // *Cause: Message sent back by the Navigator indicating an invalid trace level. // *Action: Reattempt the request with a correct trace level. / 00306, 00000, "El Connection Manager ha localizado un nivel de rastreo desconocido/incorrecto\n" // *Cause: Message sent back by the Connection Manager indicating an // invalid trace level. // *Action: Reattempt the request with a correct trace level. / 00307, 00000, "Navegador: Volver a leer los datos de parámetros" // *Cause: Request sent by the Navigator to control program indicating // that parameter data was read. // *Action: None. / 00308, 00000, "Navegador: Fallo al abrir el log mientras se releen los datos de los parámetros" // *Cause: Request sent by the Navigator to control program indicating // that it could not reopen log file after rereading parameter data. // *Action: None. / 00309, 00000, "Connection Manager: Fallo al abrir el log mientras se releen los datos de los parámetros" // *Cause: Request sent by the Connection Manager to control program // indicating that it could not reopen log file after rereading // parameter data. // *Action: None. / 00310, 00000, "Navegador: Fallo al iniciar el rastreo después de volver a leer los datos de los parámetros" // *Cause: Message sent back to control program from Navigator. // *Action: None. / 00311, 00000, "Connection Manager: Fallo al iniciar el rastreo después de volver a leer los datos de los parámetros" // *Cause: Message sent back to control program from Connection Manager. // *Action: None. / 00312, 00000, "Connection Manager: Fallo al obtener información sobre la versión" // *Cause: Message sent back to control program from Connection Manager. // *Action: None. / 00313, 00000, "Navegador: Fallo al obtener información sobre la versión" // *Cause: Message sent back to control program from Connection Manager. // *Action: None. / 00314, 00000, "Errores del adaptador de protocolo: %u,%u\n" // *Cause: Protocol Adapter errors which go with message 233 // *Action: None. / 00315, 00000, "Fallo al asignar un área de datos de conexión mayor para obtener datos del impulsor: %u\n" // *Cause: Could not allocate a large enough area to get pump statistics; // continue without them. // *Action: None. / 00316, 00000, "Se han agotado los buffers de datos en el impulsor\n" // *Cause: The Interchange is resource limited by having too few data buffers // in the pump. // *Action: If the problem persists (that is, there are a lot of log messages), // increase the number of pump buffers by increasing the value of // the parameter PUMP_BUFFERS in INTCHG.ORA. Then shutdown and restart the // Interchange to make the changes take effect. / 00317, 00000, "Fallo al contactar con el Connection Manager" // *Cause: Connection Manager is not running. // *Action: Start the Connection Manager and retry / /////////////////////////////////////////////////////////////////////////// / / 00501 - 00999 NT errors / /////////////////////////////////////////////////////////////////////////// 00501, 00000, "No se ha podido asignar memoria" // *Cause: Sufficient memory could not be allocated to perform the desired // activity. // *Action: Either free some resource for TNS or add more memory to the // machine. For further details, turn on tracing and reexecute the operation. / 00502, 00000, "Argumento no válido" // *Cause: An internal function received an invalid parameter. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 00503, 00000, "Parámetros de ADDRESS no válidos" // *Cause: An illegal set of protocol adapter parameters was specified. // *Action: Check the parameters within the ADDRESS section of the // TNSNAMES.ORA file. It may be helpful to turn on tracing and look at // the addresses specified in the trace file, checking for spelling or // other errors. Be sure to turn tracing off when the trace is complete. / 00504, 00000, "Operación no soportada" // *Cause: An internal function received a request to perform an // operation that is not supported (on this machine). // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 00505, 00000, "Time out de la operación" // *Cause: The requested operation could not be completed within the timeout // period. // *Action: For further details, turn on tracing and reexecute the operation. / 00506, 00000, "La operación se bloquearía" // *Cause: An internal operation did not commence because to do so would // block the current process and the user has requested that operations be // non-blocking. // *Action: None needed; this is an information message. / 00507, 00000, "Conexión cerrada" // *Cause: Normal "end of file" condition has been reached; partner has // disconnected. // *Action: None needed; this is an information message. / 00508, 00000, "No existe ese adaptador de protocolo" // *Cause: The protocol adapter requested for this connection does not exist. // *Action: Install the protocol adapter or use one that is available. Be // sure that the correct protocols are listed in the configuration files. / 00509, 00000, "Desbordamiento de buffer" // *Cause: Too much data for buffer. // *Action: Reexecute with larger receive buffer or smaller send buffer. / 00510, 00000, "Restricción del límite interno excedida" // *Cause: Too many files or sockets open simultaneously (or some other // resource has been depleted). // *Action: For further details, trace the operation for protocol // details. / 00511, 00000, "No hay listener" // *Cause: The connect request could not be completed because no application // is listening on the address specified, or the application is unable to // service the connect request in a sufficiently timely manner. // *Action: Ensure that the supplied destination address maatches one of // the addresses used by the listener - compare the TNSNAMES.ORA entry with // appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go // by way of an Interchange. Start the listener on the remote machine. / 00512, 00000, "La dirección ya se está utilizando" // *Cause: Specified listener address is already being used. // *Action: Start your listener with an unused address. / 00513, 00000, "Host de destino inaccesible" // *Cause: Contact cannot be made with remote party. // *Action: Make sure the network driver is functioning and the network is up. / 00514, 00000, "Los contextos tienen diferentes funciones de espera/prueba" // *Cause: Two protocol adapters have conflicting wait/test functions. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 00515, 00000, "La conexión ha fallado porque el host destino o el objeto no existen" // *Cause: The address specified is not valid, or the program being // connected to does not exist. // *Action: Ensure the ADDRESS parameters have been entered correctly; the // most likely incorrect parameter is the node name. Ensure that the // executable for the server exists (perhaps "oracle" is missing.) / 00516, 00000, "Permiso denegado" // *Cause: User has insufficient privileges to perform the requested operation. // *Action: Acquire necessary privileges and try again. / 00517, 00000, "Contacto perdido" // *Cause: Partner has unexpectedly gone away. // *Action: Investigate partner application for abnormal termination. / 00518, 00000, "Lectura o escritura incompletas" // *Cause: A data send or receive failed. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 00519, 00000, "Cuota de recursos del sistema operativo excedida" // *Cause: The current user has exceeded the allotted resource assigned in the // operating system. // *Action: Acquire more operating system resource, or perform a different // function. / 00520, 00000, "Error de sintaxis" // *Cause: The supplied connect descriptor contains illegal syntax. // *Action: Check the syntax of the connect descriptor for correct syntax. / 00521, 00000, "Falta la palabra clave" // *Cause: The supplied connect descriptor is missing one or more TNS // keywords. // *Action: Check the syntax, and ensure all required keywords are present. / 00522, 00000, "La operación ha sido interrumpida" // *Cause: An internal operation was interrupted and could not complete. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 00523, 00000, "La operación anterior estaba ocupada" // *Cause: Operation tried could not be successfully completed because // the requested resource was busy. // *Action: Attempt the operation again. If error persists, contact // Oracle Customer Support. / 00524, 00000, "La operación actual aún se está ejecutando" // *Cause: Internal operation is still in progress but will complete. // *Action: None; wait for operation to complete. / 00525, 00000, "Privilegio insuficiente para la operación" // *Cause: Operating system failed to complete operation because user // lacked sufficient privileges. // *Action: Check your platform-specific privileges. / 00526, 00000, "No hay ningún emisor (evento asíncrono falso)" // *Cause: Internal error. // *Action: For further details, turn on tracing and reexecute the operation. / 00527, 00000, "No se puede cargar el adaptador de protocolo" // *Cause: On some platforms (for example OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter // is missing or one of its supporting libraries is missing, then this // error is returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will have the name of the shared library (or DLL) that // could not be loaded. / 00528, 00000, "Adaptador de protocolo no cargado" // *Cause: On some platforms (for example OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter has not // been loaded, then this error is returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will have the name of the shared library (or DLL) that has // not been loaded. / 00530, 00000, "Error del adaptador de protocolo" // *Cause: A generic protocol adapter error occurred. // *Action: For further details, turn on tracing and reexecute the operation. / 00532, 00000, "No hay ninguna operación asíncrona anterior que atender" // *Cause: Internal protocol adapter error. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 00533, 00000, "Conexión suspendida o aún no establecida" // *Cause: Internal protocol adapter error. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 00534, 00000, "Fallo al otorgar la propiedad de la conexión al hijo" // *Cause: Internal protocol adapter error. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 00535, 00000, "Fallo al enviar o recibir el mensaje de desconexión" // *Cause: Internal protocol adapter error. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 00536, 00000, "La conexión ha pasado a un estado incorrecto" // *Cause: Internal protocol adapter error. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 00537, 00000, "El índice en la tabla del adaptador de protocolo está fuera del rango válido" // *Cause: Internal protocol adapter error. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 00539, 00000, "Los servicios de red o protocolo están desactivados" // *Cause: The Network services on or from your node are not running // or have stopped running. // *Action: Restart your network or protocol services on this platform. // If error persists, contact Oracle Customer Support. / /////////////////////////////////////////////////////////////////////////// / / 01000 - 02500 NSG errors / 01000, 00000, "spawn [] [<(ARGUMENTS='arg0, arg1,...')>]\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01001, 00000, "start [] : start listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01002, 00000, "stop [] : stop listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01003, 00000, "status [] : get the status of listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01004, 00000, "reload [] : reload the parameter files and SIDs\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01005, 00000, "trace OFF | USER | ADMIN [] : set tracing to the specified level\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01006, 00000, "set password : set the password for subsequent calls\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01007, 00000, "quit | exit : exit LSNRCTL\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01008, 00000, "version [] : get the version information of the listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01009, 00000, "service [] : get the service information of the listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01010, 00000, "dbsnmp_start : start db subagent\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01011, 00000, "dbsnmp_stop : stop db subagent\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01012, 00000, "dbsnmp_status : status db subagent\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01013, 00000,"set|show trc_{ } []: set|show trace parameters of current listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01014, 00000, "set|show log_{ } []: set|show log parameters of current listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01015, 00000, "set|show parm_name []: sets|shows current listener parm values\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01016, 00000, "change_password []: changes the password of the listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01017, 00000, "set|show current_listener []: sets|shows current listener\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01018, 00000, "save_config []: saves configuration changes to parameter file\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01019, 00000, "set rawmode ON | OFF: set output mode for services and status commands\n" // *Cause: Control program usage message. // *Action: None. // *Comment: This is a help message - do not translate. / 01020, 00000, "ESTADO del LISTENER\n" // *Cause: Control program status message. // *Action: None. / 01021, 00000, "------------------------\n" // *Cause: Control program status message. // *Action: None. / 01022, 00000, "Alias %s\n" // *Cause: Control program status message. // *Action: None. / 01023, 00000, "Versión %s\n" // *Cause: Control program status message. // *Action: None. / 01024, 00000, "Nivel de Rastreo %s\n" // *Cause: Control program status message. // *Action: None. / 01025, 00000, "Seguridad %s\n" // *Cause: Control program status message. // *Action: None. / 01026, 00000, "Fecha de Inicio %s\n" // *Cause: Control program status message. // *Action: None. / 01027, 00000, "Fichero de Rastreo del Listener %s\n" // *Cause: Control program status message. // *Action: None. / 01028, 00000, "Fichero Log del Listener %s\n" // *Cause: Control program status message. // *Action: None. / 01029, 00000, "Resumen de servicios...\n" // *Cause: Control program status message. // *Action: None. / 01030, 00000, "El listener no soporta ningún servicio\n" // *Cause: Control program status message. // *Action: None. / 01033, 00000, "Fichero de Parámetros del Listener %s\n" // *Cause: Control program status message. // *Action: None. / 01034, 00000, "Tiempo de actividad %lu días %lu hr. %lu min. %lu seg.\n" // *Cause: Control program status message. // *Action: None. / 01036, 00000, "%s establecido:%s rechazado:%s" // *Cause: Control program status message. // *Action: None. / 01037, 00000, "%s establecido:%s rechazado:%s" // *Cause: Control program status message. // *Action: None. / 01038, 00000, "%s establecido:%s rechazado:%s actual:%s máx:%s estado:%s" // *Cause: Control program status message. // *Action: None. / 01039, 00000, "%s\t\ttiene %s gestor(es) de servicio" // *Cause: Control program status message. // *Action: None. / 01040, 00000, "SNMP %s\n" // *Cause: Control program status message. // *Action: None. / 01041, 00000, "%s parámetro \"%s\" establecido en %s\n" // *Cause: Control program status message. // *Action: None. / 01042, 00000, "El listener actual es %s\n" // *Cause: Control program status message. // *Action: None. / 01043, 00000, "Clave cambiada para %s\n" // *Cause: Control program status message. // *Action: None. / 01044, 00000, "%s(Registrado)\t\ttiene %s gestor(es) de servicio" // *Cause: Control program status message. // *Action: None. / 01045, 00000, "%s(No Registrado)\t\ttiene %s gestor(es) de servicio" // *Cause: Control program status message. // *Action: None. / 01046, 00000, "Se han guardado %s parámetros de configuración.\n" // *Cause: Control program status message. // *Action: None. / 01047, 00000, "Fichero de Parámetros Antiguo %s\n" // *Cause: Control program status message. // *Action: None. / 01048, 00000, "No hay cambios que guardar para %s.\n" // *Cause: Control program status message. // *Action: None. / 01049, 00000, "%s (%s)\t\ttiene %s manejador(es) de servicio" // *Cause: Control program status message. // *Action: None. / 01050, 00000, "%s" // *Cause: Control program general message. // *Action: None. / 01052, 00000, "El comando se ha ejecutado correctamente\n" // *Cause: Control program general message. // *Action: None. / 01053, 00000, "Conectándose a %s\n" // *Cause: Control program general message. // *Action: None. / 01054, 00000, "Contacto establecido correctamente con el listener\n" // *Cause: Control program general message. // *Action: None. / 01055, 00000, "Listener parado correctamente\n" // *Cause: Control program general message. // *Action: None. / 01057, 00000, "Nombre del programa: %s\n" // *Cause: Control program general message. // *Action: None. / 01058, 00000, "Argumentos : %s\n" // *Cause: Control program general message. // *Action: None. / 01059, 00000, "Entorno : %s\n" // *Cause: Control program general message. // *Action: None. / 01060, 00000, "La clave se ha definido como %s\n" // *Cause: Control program general message. // *Action: None. / 01061, 00000, "La clave no se ha definido\n" // *Cause: Control program general message. // *Action: None. / 01062, 00000, "El subagente de base de datos ya está en ejecución.\n" // *Cause: Control program general message. // *Action: None. / 01063, 00000, "El subagente de base de datos no se ha arrancado.\n" // *Cause: Control program general message. // *Action: None. / 01064, 00000, "Los cambios en la configuración del listener no se mantendrán\n" // *Cause: Configuration changes to the listener will not be // visible when the listener starts up again as the check-pointing // has been turned off in listener.ora // *Action: Edit LISTENER.ORA setting USE_CKPFILE_LISTENER=true / 01065, 00000, "El modo raw es %s\n" // *Cause: Control program general message. // *Action: None. / 01070, 00000, "Arrancando %s: por favor, espere...\n\n" // *Cause: Listener starting message. // *Action: None. / 01071, 00000, "%s está establecido como %s\n" // *Cause: Listener starting message. // *Action: None. / 01072, 00000, "Arrancado en %s\n" // *Cause: Listener starting message. // *Action: None. / 01073, 00000, "Escuchando: %s\n" // *Cause: Listener starting message. // *Action: None. / 01074, 00000, "Se ha intentado escuchar en: %s\n" // *Cause: Listener starting message. // *Action: None. / 01075, 00000, "Fichero log abierto: %s\n" // *Cause: Listener starting message. // *Action: None. / 01076, 00000, "Fichero de rastreo abierto: %s\n" // *Cause: Listener starting message. // *Action: None. / 01077, 00000, "Fichero de parámetros abierto: %s\n" // *Cause: Listener starting message. // *Action: None. / 01078, 00000, "Fichero de consulta de nombres abierto: %s\n" // *Cause: Listener starting message. // *Action: None. / 01079, 00000, "Se ha intentado conectar: %s\n" // *Cause: Listener starting message. // *Action: None. / 01093, 00000, "%s * %s * %d" // *Cause: Listener logging message. // *Action: None. / 01094, 00000, "%s * %d" // *Cause: Listener logging message. // *Action: None. / 01095, 00000, "%s * %s * %s * %d" // *Cause: Listener logging message. // *Action: None. / 01096, 00000, "%s * %s * %s * %s * %s * %d" // *Cause: Listener logging message. // *Action: None. / 01097, 00000, "TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE" // *Cause: Listener logging message. // *Action: None. / 01100, 00000, "TNS ha devuelto un error %d al intentar arrancar el listener" // *Cause: The bequeath (BEQ) mechanism that LSNRCTL uses to start the listener // failed. // *Action: Check to ensure that the BEQ driver is installed - if it is not then // the nserror code returned will be 12538 (NSENODRIVER). To fix this, reinstall // SQL*Net V2 and make sure that the BEQ driver is selected when it is // installed. If this is not the problem then the error is probably caused // by the fact that the TNSLSNR executable cannot be found in the place // expected in your platform's ORACLE environment. Verify that the full // pathname of the TNSLSNR executable as displayed by LSNRCTL is correct. / 01101, 00000, "No se ha podido encontrar el nombre del servicio %s" // *Cause: The ervice name could not be resolved by name-lookup. // *Action: Verify that the listener name or service name specified to // LSNRCTL has the correct name and address defined in LISTENER.ORA or in // TNSNAMES.ORA. / 01102, 00000, "La aplicación TNS contactada no era el listener" // *Cause: Another TNS application such as the Interchange was listening // at the address contacted. There may be another TNS application listening // at the address contacted and the data returned is not in the appropriate // format. // *Action: Verify that the listener name or service name specified to // LSNRCTL has the correct name and address defined in LISTENER.ORA or in // TNSNAMES.ORA. / 01103, 00000, "El componente de la dirección correspondiente al protocolo no está especificado correctamente" // *Cause: The ADDRESS used to contact the listener is not correctly specified. // This error occurs because the address fails to specify the destination // of the listener. The address is well formed (for example, there are no // missing parentheses) but it is missing a protocol specific component. For // example, this is the error returned when the HOST component is missing from // a TCP/IP address string. // *Action: Edit the ADDRESS in LISTENER.ORA to include the required // protocol-specific keywords. For more information about the keywords // required by different protocol adapters, see the Oracle operating system // specific documentation for your platform. / 01106, 00000, "El listener que usa el nombre de listener %s ya ha sido arrancado" // *Cause: Another listener is already listening on one of the ADDRESSes // specified. // *Action: Shutdown the previous listener specified by the listener name // before starting this one. / 01107, 00000, "No se ha especificado ningún nivel de rastreo válido" // *Cause: Failed to specify a valid trace level for the LSNRCTL trace command. // *Action: Specify one of OFF, USER, or ADMIN. // Type "LSNRCTL help trace" for more information or consult Chapter 2 of // this manual for an introduction to the concepts of tracing. / 01108, 00000, "El prompt de la clave del listener ha fallado" // *Cause: Password not entered via tty // *Action: Enter the listener password on a tty device / 01109, 00000, "El código cifrado de la clave del listener ha fallado" // *Cause: Possibly garbled password entered // *Action: Re-enter the listener password, using valid ASCII characters. If // problem persists, contact Oracle Customer Support. / 01110, 00000, "No coinciden - clave no cambiada" // *Cause: New password and reentered new password are different" // *Action: Re-enter the listener password, make sure that New password // and reentered new password are the same / 01111, 00000, "El estado del log puede ser ON u OFF" // *Cause: Failed to specify a log status value for the LSNRCTL log_status command. // *Action: Specify one of ON or OFF. // Type "LSNRCTL help set log_status" for more information or consult Chapter 2 of // this manual for an introduction to the concepts of logging. 01112, 00000, "Plug and play puede ser ON u OFF" // *Cause: Failed to specify a valid value for the LSNRCTL use_plugandplay command. // *Action: Specify one of ON or OFF. // Type "LSNRCTL help set use_plugandplay" for more information. / 01113, 00000, "save_config_on_stop puede ser ON u OFF" // *Cause: Failed to specify a valid value for the LSNRCTL save_config_on_stop command. // *Action: Specify one of ON or OFF. // Type "LSNRCTL help set save_config_on_stop" for more information. / 01150, 00000, "La dirección del nombre de listener especificado no es correcta" // *Cause: The address on which the listener attempted to listen contains a // syntax error. // *Action: For the listener name or service name specified to LSNRCTL, check // that the address or connect descriptor is well-formed. You can find the // listener name in LISTENER.ORA, or you can access the listener through // the service name is TNSNAMES.ORA. / 01151, 00000, "Falta el nombre del listener, %s, en LISTENER.ORA" // *Cause: The listener could not find the listener name specified. // *Action: Make sure valid addresses on which to listen are specified for the // listener name in LISTENER.ORA. / 01152, 00000, "Todas las direcciones especificadas para el nombre de listener, %s, han fallado" // *Cause: The listener failed to listen on any of the specified addresses. // *Action: Make sure that another application is not listening on the addresses // specified or check that the appropriate protocol adapters are installed. // Turn on tracing and execute again for more information. / 01153, 00000, "No se ha podido procesar la cadena de caracteres: %s" // *Cause: The string specified is not well-formed. // *Action: Not normally visible to the user. For further details, // turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. // *Comment: Do not include in error manual. / 01154, 00000, "Detectado un SID con un formato antiguo que ya no está soportado" // *Cause: One of the SIDs was specified in an obsolete format. // *Action: Check LISTENER.ORA for a line of the form: // = (SID=(ORACLE_HOME=)) OR // = (SID_DESC=(ORACLE_HOME=)) // The above format is no longer supported and SID_LIST_ // format described in the Net8 Administrator's Guide should be used. // For example, // SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=)(ORACLE_HOME=))) / 01155, 00000, "Parámetro SID_LIST_%s especificado incorrectamente en LISTENER.ORA" // *Cause: SID_LIST_ in LISTENER.ORA has an error in it. // *Action: Be sure this parameter is specified as described in the // Net8 Administrator's Guide. For example, // SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=)(ORACLE_HOME=))) / 01156, 00000, "Faltan los parámetros PROTOCOL, TIMEOUT o POOL_SIZE de PRESPAWN_DESC o son incorrectos" // *Cause: PRESPAWN_DESC in each SID_DESC does not have required fields. // *Action: Be sure the parameters required for PRESPAWN_DESC are specified // in each SID_DESC. For example, // SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=)(PRESPAWN_MAX=5)(ORACLE_HOME=)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30)))) // Add or correct these parameters in the LISTENER.ORA file / 01157, 00000, "Sólo puede escuchar en %d direcciones - se ignorará %s" // *Cause: Too many addresses were given to listen on. // *Action: Reduce the number of addresses to listen on and use another // listener to listen on the remaining addresses. / 01158, 00000, "Ha alcanzado el límite de conexión interna, lo que impide que el distribuidor se conecte" // *Cause: The internal SQL*Net connection list is full. Too many // dispatchers are connected to the listener; therefore, no more dispatchers // are allowed to connect. // *Action: For further details, turn on tracing and reexecute the // operation. If error persists, contact Oracle Customer Support. / 01159, 00000, "Ha alcanzado el límite de conexión interna, el listener se ha desconectado" // *Cause: The internal SQL*Net connection list is full. The listener is // configured to use too many SQL*Net connections. // *Action: Reduce the number of listen addresses or services connected to // the listener. For further details, turn on tracing and reexecute the // operation. If error persists, contact Oracle Customer Support. / 01160, 00000, "No ha especificado el nivel de rastreo" // *Cause: Failed to specify a trace level for the trace command. // *Action: Specify one of OFF, USER, or ADMIN. // Users should not see this error if LSNRCTL is being used. // *Comment: Do not include in error manual. / 01161, 00000, "No se ha encontrado el alias %s. Compruebe el fichero de parámetros del listener" // *Cause: The alias specified to spawn a program was not found in LISTENER.ORA. // *Action: This is not seen in normal use of SQL*Net. // *Comment: See the porting notes or internal documentation on how to have // the listener spawn a process. // Do not include in error manual. / 01162, 00000, "Error de sintaxis en la dirección resuelta del alias %s" // *Cause: The alias specified to spawn a program was not a valid NVstring. // *Action: This is not seen in normal use of SQL*Net. // *Comment: See the porting notes or internal documentation on how to have // the listener spawn a process. // Do not include in error manual. / 01163, 00000, "No se ha podido originar el proceso %s" // *Cause: The process failed to start correctly. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Turn on tracing in the listener and execute again. This problem is // most often caused by the executable specified to be missing from the PATH // in the listener's environment. See the porting notes or internal documentation // on how to have the listener spawn a process. // Do not include in error manual. / 01164, 00000, "No se ha enviado ningún alias de producción al listener" // *Cause: The spawn command was issued without an alias. // *Action: This is not seen in normal use of SQL*Net. // *Comment: See the porting notes or internal documentation on how to have // the listener spawn a process. Users should not see this error if LSNRCTL // is being used. // Do not include in error manual. / 01165, 00000, "El alias de producción no tiene ningún nombre de programa definido" // *Cause: The spawn alias in LISTENER.ORA is incorrectly specified. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Make sure the NAME component of the PROCESS description is set. // Do not include in error manual. / 01167, 00000, "El listener contactado no soporta el comando %s" // *Cause: The listener does not recognize the command. // *Action: This is caused when a newer version of LSNRCTL contacts an old // listener. Upgrade listener if executing this command is important. / 01168, 00000, "No se puede asignar memoria" // *Cause: Sufficient memory could not be allocated to perform the desired // activity. // *Action: Either free some resource for TNS, or add more memory to the // machine. For further details, turn on tracing and reexecute the operation. / 01169, 00000, "El listener no ha reconocido la clave" // *Cause: The security feature of the listener is preventing the intended // operation. // *Action: Some commands like stopping the listener are only intended to be // done by DBAs. A client can only use LSNRCTL to get the status of a listener // and the version of the listener software running. The command that the // client attempted may not have been appropriate. If a DBA is attempting // the command then use the "set password" command at the LSNRCTL prompt // with one of the appropriate passwords in the PASSWORDS_ entry // in LISTENER.ORA. If you do not know a password then you are trying to // execute an inappropriate command. / 01170, 00000, "Detección de eventos interrumpida para la dirección %s" // *Cause: The event detection mechanism for the address specified returned // an error. // *Action: Future attempts to detect events on this address will fail. // The listener will deallocate the listen address and connections will no // long be accepted for this address. This error is not normally visible // to the user. For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 01171, 00000, "Detección de eventos interrumpida para el distribuidor %s" // *Cause: The event detection mechanism for the dispatcher specified returned // an error. // *Action: Future attempts to detect events on this dispatcher will fail. // The listener will deallocate the dispatcher and connections will no // long be redirected to this dispatcher. This error is not normally visible // to the user. For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 01172, 00000, "El listener se ha parado, ya que se ha revocado la asignación de todas las direcciones de recepción" // *Cause: The event detection mechanism broke and caused all listen addresses // to be removed. // *Action: Error 1170 has occured and caused all the listen addresses to be // deallocated. Since all the listen addresses have been removed, // no more connections can be established to this listener so it shuts itself // down. This error is not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 01173, 00000, "Falta el parámetro PRESPAWN_MAX de SID_DESC o es incorrecto" // *Cause: PRESPAWN_MAX in each SID_DESC does not have required fields. // *Action: Be sure the parameters required for PRESPAWN_DESC are specified // in each SID_DESC. For example, // SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=)(PRESPAWN_MAX=15)(ORACLE_HOME=)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30)))) // Add or correct these parameters in the LISTENER.ORA file / 01174, 00000, "La suma de los POOL_SIZEs de cada PRESPAWN_DESC es mayor que el PRESPAWN_MAX" // *Cause: The minimum value for PRESPAWN_MAX should be the sum of the POOL_SIZEs. // *Action: Be sure the parameters required for PRESPAWN_DESC are specified // in each SID_DESC. For example, // SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=)(PRESPAWN_MAX=15)(ORACLE_HOME=)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30))(PRESPAWN_DESC=(PROTOCOL=ipc)(POOL_SIZE=5)(TIMEOUT=15)))) // Add or correct these parameters in the LISTENER.ORA file 01175, 00000, "Clave no cambiada\n" // *Cause: Unable to set the new password // *Action: Be sure to see that the new password has legal ASCII // characters. Try to set the password again. / 01176, 00000, "Error al cargar el nuevo valor de parámetro\n" // *Cause: Illegal values given for the parameters // *Action: Make sure that the parameter values are valid // refer to the manual for the legal values for paramters / 01177, 00000, "Estado de log es OFF. No ha cambiado el fichero log/directorio de logs\n" // *Cause: Log status needs to be set ON for changing the log file // *Action: use command set log_status ON to set the log status of the // listener ON. / 01178, 00000, "Nivel de rastreo es 0. No cambia el fichero rastreo/directorio fich. rastreo\n" // *Cause: Trace Levelneeds to be set for changing the trace file/directory // *Action: use command set trc_level ON to set the trace level / 01200, 00000, "El listener debe ser la raíz del identificativo de usuario del sistema" // *Cause: The ownership privileges of the TNSLSNR executable are incorrect. // *Action: Contact your DBA or system administrator to change the ownership // of the file to be suid root and restart the listener. This action is // necessary because the user that started the process should claim // ownership. // *Comment: This error is reported only on Trusted Oracle platforms. / 01201, 00000, "El listener no puede encontrar el ejecutable %s para SID %s" // *Cause: The executable for the Oracle dedicated server process cannot be // found. // *Action: Check the appropriate SID_DESC in LISTENER.ORA to make sure that // the ORACLE_HOME component is pointing to a valid location. If this component // is not set, then check the value of the ORACLE_HOME environment variable. // *Comment: This error is reported only on UNIX platforms. / 01202, 00000, "Falta el grupo del ABD(%s) especificado por DBA_GROUP en SID_DESC" // *Cause: The dba group specified is missing from /ETC/GROUP. // *Action: Check the DBA_GROUP parameter in the SID_DESC in LISTENER.ORA // and verify it has a valid entry in /ETC/GROUP. // *Comment: This error is reported only on UNIX platforms. / 01203, 00000, "Falta la cuenta (%s) especificada por DEFAULT_USER_ACCOUNT en SID_DESC" // *Cause: The unprivileged OS account is missing from /etc/passwd. // *Action: Check the DEFAULT_USER_ACCOUNT parameter in the SID_DESC in // LISTENER.ORA and verify it has a valid entry in /etc/passwd. This is // the account that the Oracle shadow process will be started with if the // the connecting client has database privileges or does not exist on this // machine. // *Comment: This error is reported only on UNIX platforms. / 01204, 00000, "La cuenta sin privilegios (%s) está en el grupo del ABD (%s)" // *Cause: The unprivileged account has DBA privileges. The unprivileged // account specified by DEFAULT_USER_ACCOUNT in the SID_DESC in // LISTENER.ORA is a member of the dba group specified by DBA_GROUP in // SID_DESC. The unprivileged account cannot belong to the dba group // because this would be a security violation with OPS$ logins. // *Action: Remove the unprivileged account from the dba group. // *Comment: This error is only reported on UNIX platforms. / 01300, 00000, "\nERROR en %s\n" // *Cause: Listener logging message. // *Action: None. / 01301, 00000, "Estructura de error de TNS:" // *Cause: Listener logging message. // *Action: None. / 01302, 00000, "código de error de nr: %d" // *Cause: Listener logging message. // *Action: None. / 01303, 00000, "código de error principal de ns: %d" // *Cause: Listener logging message. // *Action: None. / 01304, 00000, "código de error secundario de ns: %d" // *Cause: Listener logging message. // *Action: None. / 01305, 00000, "código de error principal de nt: %d" // *Cause: Listener logging message. // *Action: None. / 01306, 00000, "código de error secundario de nt: %d" // *Cause: Listener logging message. // *Action: None. / 01307, 00000, "código de error del SO de nt: %d" // *Cause: Listener logging message. // *Action: None. / / --------SNSGUM:Connection Load Balancer Errors 2401-2500---------------- / 02401, 00000, "gbname %s demasiado largo, %d caracteres permitidos" // *Cause: gbname or domain name too long. // *Action: Check the gbname parameter in listener.ora, shorten it. / 02402, 00000, "Parámetro CLBGNAMES incorrecto en tnsnames.ora" // *Cause: CLBGNAMES parameter in tnsnames.ora is bad. // *Action: Check the CLBGNAMES parameter format and correct it. Make sure // that the tnsnames.ora file is there. / 02403, 00000, "Alias %s incorrecto o no existe en tnsnames.ora" // *Cause: An alias was expected in tnsnames.ora but was not found or was not // correctly formed. // *Action: Check the tnsnames.ora for the alias and make sure it is correctly // formed. / 02404, 00000, "El servicio %s no contiene manejadores locales" // *Cause: The listener found no suitable handler to redirect to. // *Action: Make sure that there is at least one handler for this node. / 02405, 00000, "Fallo en la llamada GMS, compruebe los logs de GMS." // *Cause: A GMS call made by the listener failed. // *Action: Check if the GMS is up and running. See GMS-client trace files // for more information. / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / ----------------------- NA internal errors ------------------------------ / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / Reserved for NAtive service errors: 2501 - 3500 02501, 00000, "Authentication: no more roles" // *Cause: When a process attempted to retrieve a role from the authentication // service, no more were available. // *Action: None. This error is used internally and occurs in the normal course // of events. / 02502, 00000, "Authentication: unable to find initialization function" // *Cause: The native authentication service was unable to call the // initialization function for the specified service because // it does not exist. // *Action: If this service adaptor came directly from Oracle, contact // Oracle Customer Support, as this error should never // happen. Otherwise, add an initialization function for the // service being used. / 02503, 00000, "Parameter retrieval failed" // *Cause: The native service layer was unable to retrieve a parameter from a // configuration file. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02504, 00000, "Parameter count retrieval failed" // *Cause: The native service layer was unable to determine the number of // arguments given for a configuration parameter. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02505, 00000, "Authentication: null context pointer provided" // *Cause: The function nau_ini() was passed a null pointer as the pointer to // the context that it is supposed to use. // *Action: Call nau_ini() with a pointer to a context structure. / 02506, 00000, "Authentication: no type string" // *Cause: An authentication context structure does not contain a string that // describes the authentication service being used. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02507, 00000, "Encryption: algorithm not installed" // *Cause: After picking an algorithm, the server was unable to find // an index for it in its table of algorithms. This should // be impossible because the algorithm was chosen // (indirectly) from that list. // *Action: Not normally visible to the user. For further details, // turn on tracing and reexecute the operation. If error // persists, contact Oracle Customer Support. / 02508, 00000, "Encryption: server negotiation response in error" // *Cause: The server's response in negotiation was in error. // *Action: Not normally visible to the user. For further details, // turn on tracing and reexecute the operation. If error // persists, contact Oracle Customer Support. / 02509, 00000, "Authentication: invalid process state" // *Cause: The state in which a process is running does not correspond to any // of the values which are valid. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02510, 00000, "Invalid numeric data type" // *Cause: The type of a piece of numeric data that was received does not // correspond to one of the valid values. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02511, 00000, "Invalid data type" // *Cause: The type of a piece of data that was received or to be transmitted // did not correspond to any of the correct values. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02512, 00000, "Invalid status received" // *Cause: A process received a value as a status flag which was unknown. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02513, 00000, "Requested data type does not match retrieved type" // *Cause: A service requested data whose type does not match that of the segment // which was sent from the other process. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02514, 00000, "Invalid packet received" // *Cause: A process received a data packet which was not meant for the native // services layer. // *Action: If it is possible, enable tracing and attempt to reproduce the // problem. // In any event, contact Oracle Customer Support. / 02515, 00000, "Encryption/crypto-checksumming: unknown control type" // *Cause: An encryption or crypto-checksumming algorithm "control" // function was called, but did not recognize the "type" // argument it was given. // *Action: Not normally visible to the user. For further details, // turn on tracing and reexecute the operation. If error // persists, contact Oracle Customer Support. / 02516, 00000, "No data available" // *Cause: A native service attempted to retrieve data but no data was // available to be received. // *Action: The error is not normally visible as it usually is only used to // signal the end of a data stream. If the error becomes visible, // enable tracing to reproduce the problem and contact // Oracle Customer Support. / 02517, 00000, "key smaller than requested size" // *Cause: The key returned by negotiation was smaller than // the size requested by some service (either encryption or // crypto-checksumming). // *Action: The error is not normally visible. If the error persists, // enable tracing to reproduce the problem and contact // Oracle Customer Support. / 02518, 00000, "key negotiation error" // *Cause: An error occurred while the two sides of the connection // were negotiating an encryption or crypto-checksumming key. // *Action: The error is not normally visible. If the error persists, // enable tracing to reproduce the problem and contact // Oracle Customer Support. / 02519, 00000, "no appropriate key-negotiation parameters" // *Cause: No appopriate key-negotiation parameters are available for // the key size requested either by encryption or by crypto- // checksumming. // *Action: The error is not normally visible. Enable tracing to // reproduce the problem and contact Oracle Customer // Support. / 02520, 00000, "encryption/crypto-checksumming: no Diffie-Hellman seed" // *Cause: The "sqlnet.crypto_seed" parameter is missing from the // SQLNET.ORA parameters file for SQL*Net. // *Action: Add this line to SQLNET.ORA: // sqlnet.crypto_seed = "randomly-chosen text" / 02521, 00000, "encryption/crypto-checksumming: Diffie-Hellman seed too small" // *Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA // parameter file for SQL*Net is too small. // *Action: Add more randomly-chosen text to it. / 02524, 00000, "Authentication: privilege check failed" // *Cause: An error occurred when the SQL*Net authentication service attempted // to verify that a user had a specific database privilege. // *Action: This error should not happen normally. Enable tracing and attempt // to repeat the error. Contact Customer Support. / 02525, 00000, "encryption/crypto-checksumming: self test failed" // *Cause: The ANO encryption/crypto-checksumming service detected an error // while running tests on the active encryption or checksumming // algorithm. // *Action: Contact Customer Support. / 02526, 00000, "server proxy type does not match client type" // *Cause: The authentication type selected by the server does not match that // picked by the client. // *Action: Contact Oracle Customer Support / /////////////////////////////////////////////////////////////////////////// / / 03501 - 03600 NSPING (not reportable to OSN) - NS ping utility / 03501, 00000, "OK" // *Cause: The operation succeeded. // *Action: No action necessary. / 03502, 00000, "Argumentos insuficientes. Sintaxis: tnsping []" // *Cause: Some required command-line arguments are missing. // *Action: Re-enter the command using the correct arguments. / 03503, 00000, "No se ha podido inicializar el lenguaje nacional (NL)" // *Cause: The network library could not be initialized. // *Action: This is an internal error which should not normally be visible. // Ensure that memory is available to run the application and that // there are no other operating system problems, and then attempt // the command again. / 03504, 00000, "Nombre de servicio demasiado largo" // *Cause: The service name you are attempting to ping is too long. // *Action: Re-enter the command using the correct service name. / 03505, 00000, "Fallo al resolver el nombre" // *Cause: The service name you provided could not be found in TNSNAMES.ORA, // an Oracle Names server, or a native naming service. // *Action: Verify that you entered the service name correctly. You may need // to ensure that the name was entered correctly into the network // configuration. / 03506, 00000, "Fallo al crear el enlace de dirección" // *Cause: The TNSPING utility found the requested address or service name, // but received an internal error when trying to use it. // *Action: This is an internal error which should not normally be visible. // Ensure that memory is available to run the application and that // there are no other operating system problems, and then attempt // the command again. / 03507, 00000, "Fallo al buscar la palabra clave ADDRESS" // *Cause: The TNS address did not contain an ADDRESS keyword. // *Action: If you entered the TNS address on the command line, be sure that // the syntax is correct. If you entered a service name on the // command line, the address contains the wrong information. You // should verify that the information was entered correctly. / 03508, 00000, "Fallo al crear la cadena de dirección" // *Cause: The TNSPING utility received an internal error when generating // an address. // *Action: This is an internal error which should not normally be visible. // Ensure that memory is available to run the application and that // there are no other operating system problems, and then attempt // the command again. / 03509, 00000, "Realizado correctamente (%d mseg)" // *Cause: The operation succeeded, in this amount of time. // *Action: No action necessary. / 03510, 00000, "Fallo debido a un error de E/S" // *Cause: An I/O operation failed, perhaps due to a resource failure // or premature window termination. // *Action: This is an internal error which should not normally be visible. // Do not close the TNSPING window before all I/O operations have // completed. / /////////////////////////////////////////////////////////////////////////// / / 03601 - 03700 NSUT (not reportable to OSN) - NS trace route utility / 03601, 00000, "Fallo en la recogida de información de la ruta" // *Cause: The route could either not connect, or encountered an // unsupported version of SQL*Net. // *Action: Check if SQL*Net along all nodes is version 2.3 or // greater. / 03602, 00000, "Argumentos insuficientes. Sintaxis: trcroute " // *Cause: Some required command-line arguments are missing. // *Action: Re-enter the command using the correct arguments. / 03603, 00000, "Se ha encontrado un nodo con una versión anterior a 2.3 de SQL*Net" // *Cause: Any version of SQL*Net before 2.3 doesn't support // trcroute. // *Action: Find the node that isn't responding to trcroute. / /////////////////////////////////////////////////////////////////////////// / / 04001 - 04200 NFP errors / /////////////////////////////////////////////////////////////////////////// / / The range 04001 to 04200 should be reserved for the Connection Manager. / The messages will include status messages / as well as error messages. / / Start with error messages first. / // UI[04001,04200] 04001, 00000, "CMCTL: error al obtener la línea de comandos del terminal" // *Cause: Improper standard input connection from the terminal. // *Action: Normally not visible to the user. Start the CMCTL program again. // If error persists, contact Oracle Customer Support. / 04002, 00000, "CMCTL: error al iniciar el Connection Manager" // *Cause: The Connection Manager could not be started. // *Action: Check the Connection Manager configuration file // for errors and confirm that no other programs are using // the ADDRESS(es) specified. If error continues, turn on tracing in the // Connection Manager and examine the trace files to determine the // cause of the problem. Be sure to turn tracing off when the problem has // been rectified. / 04003, 00000, "CMCTL: error al enviar la solicitud al Connection Manager" // *Cause: Improper command sent to the Connection Manager or the Connection // Manager is not responding. Not normally visible to the user. // *Action: Verify that the command sent to the Connection Manager is valid. // Also check that the Connection Manager is running by using the CMCTL STATUS // command. If necessary, start the Connection Manager using the CMCTL START // command. / 04004, 00000, "CMCTL: error al iniciar el Connection Manager Admin" // *Cause: The Connection Manager Admin could not be started. // *Action: Check to make sure that executable for the Connection Manager // Admin (cmadmin) exist in the ORACLE home directory. // If error continues, turn on tracing in the Connection Manager Admin // and examine the trace file to determine the cause of the // problem. Be sure to turn tracing off when the problem has been // rectified. / 04005, 00000, "CMCTL: error al enviar la solicitud al Connection Manager Admin" // *Cause: The Connection Manager Admin is not responding or is not // running. // *Action: Check that the Connection Manager Admin is running by using the // CMCTL STATUS command. If necessary, start the Connection Manager Admin using // the CMCTL START command. / 04006, 00000, "CMCTL: variable HOST no definida" // *Cause: The HOST variable was not set. // *Action: Set the variable HOST properly and restart the CMCTL program. / 04007, 00000, "CMCTL: host desconocido" // *Cause: The pointer HOST is set to an unknown hostname. // *Action: Set the pointer HOST properly and restart CMCTL program. / 04008, 00000, "CMCTL: no se ha podido contactar con el Connection Manager" // *Cause: Connection could not be properly established to a Connection Manager. // This may be because the Connection Manager specified is not running. // *Action: Check that the Connection Manager is running by using the STATUS // command. If necessary, start the Connection Manager // using the START command. // If it is running and the error persists, contact Oracle Customer // Support. / 04009, 00000, "CMCTL: no se ha podido contactar con el Connection Manager Admin" // *Cause: Connection could not be properly established to a Connection // Manager Admin. This may be because the Connection Manager Admin // specified is not running. // *Action: Make sure the Connection Manager Admin is running by using the STATUS // command. If necessary, start the // Connection Manager Admin using the START command. // If it is running and the error persists, contact Oracle Customer // Support. / 04010, 00000, "Error al vaciar el contexto NS" // *Cause: Internal NS error; connection may be lost. // *Action: Make sure the connection is properly established. If the // error persists, then contact Oracle Customer Support. / 04011, 00000, "CMCTL: error al ejecutar el comando de desconexión de NS" // *Cause: Internal NS error. Error in closing down connections. // *Action: Make sure the networking protocol being used is properly // installed on the machine. If the error persists contact // Oracle Customer Support. / 04012, 00000, "CMCTL: error al abrir el canal de entrada del terminal" // *Cause: Could not open standard terminal input. Internal error. // *Action: Normally not visible to the user. Restart the CMCTL program. // If error persists, contact Oracle Customer Support. / 04013, 00000, "CMCTL: error al cerrar el canal de entrada del terminal" // *Cause: Could not close terminal input channel. Internal error. // *Action: Normally not visible to the user. Restart the CMCTL program. // If error persists, contact Oracle Customer Support. / 04014, 00000, "CMCTL: error al ejecutar el comando de envío de NS" // *Cause: Internal NS error. Connection may be lost. // *Action: If the error persists contact Oracle Customer Support. / 04015, 00000, "CMCTL: error al ejecutar el comando de recepción de NS" // *Cause: Internal NS error. Connection may be lost. // *Action: If the error persists contact Oracle Customer Support. / 04016, 00000, "CMCTL: error al inicializar la interfaz de idioma nacional" // *Cause: The message file could not be found. // *Action: Make sure that the ORACLE environment is set and that the message // file is in the correct place. / 04017, 00000, "CMCTL: faltan datos de Connection Manager en CMAN.ORA" // *Cause: CMAN.ORA does not contain Connection Manager data. // *Action: Define the correct data for the Connection Manager, then restart // the CMCTL program. / 04018, 00000, "CMCTL: falta el nombre de Connection Manager en el fichero de configuración" // *Cause: CMAN.ORA does not contain a CMANAGER_NAME component. // *Action: Define the correct name for the CMANAGER_NAME, then restart // the CMCTL program. / 04019, 00000, "CMCTL: falta una o más ADDRESS en los ficheros de configuración" // *Cause: Configuration files do not contain an ADDRESS/ADDRESS_LIST // component. // *Action: Define the Connection Manager ADDRESS(es) in the CMAN.ORA // file and then restart the CMCTL program. / 04020, 00000, "CMCTL: No se ha podido contactar con el Connection Manager Admin" // *Cause: The Connection Manager Admin is not running. // *Action: Verify that the Connection Manager Admin is running by doing a status // request on the Connection Manager Admin. // If necessary, start the Connection Manager Admin using the START command. / 04021, 00000, "CMCTL: El entorno ORACLE está definido incorrectamente" // *Cause: The ORACLE environment is incorrectly set up. // *Action: Refer to the Oracle operating system specific documentation for // your platform for information on how the ORACLE environment should be set. // Correct it and rerun CMCTL. Make sure the ORACLE environment includes // the correct directories. / 04022, 00000, "CMCTL: No se ha podido resolver el nombre/dirección de Connection Manager" // *Cause: The Connection Manager's name to address definition is missing. // *Action: Check TNSNAMES.ORA file and make sure to include a definition for // the name specified. / 04023, 00000, "CMCTL: No se ha podido resolver el nombre/dirección de Connection Manager Admin" // *Cause: The Connection Manager Admin's name to address definition is missing. // *Action: Check TNSNAMES.ORA file and make sure to include a definition for // the name specified. / 04031, 00000, "CMCTL: error NT interno" // *Cause: Problem interfacing to the protocol adapters installed. // *Action: Normally not visible to the user. Try starting CMCTL // again. If the error persists, check the product installation. If it is // correct, contact Oracle Customer Support. / 04032, 00000, "CMCTL: error NS interno" // *Cause: Problem interfacing with TNS. // *Action: Normally not visible to the user. Try starting CMCTL // again. If the error persists, check the product installation. If it is // correct, contact Oracle Customer Support. / 04033, 00000, "CMCTL: error NL interno" // *Cause: Problem with internal TNS module NL. // *Action: Normally not visible to the user. Try starting CMCTL // again. If the error persists, check the product installation. If it is // correct, contact Oracle Customer Support. / 04034, 00000, "CMCTL: error NFP interno" // *Cause: Problem with internal Connection Manager. // *Action: Normally not visible to the user. Try starting CMCTL // again. If the error persists, check the product installation. If it is // correct, contact Oracle Customer Support. / 04035, 00000, "CMCTL: error al general en nombre de fichero completo" // *Cause: Problem while constructing the full path for a file name because // the path name to the file or the environment variables are // incorrect. Files looked up include CMAN.ORA // and the error files for the Connection Manager and Connection Manager Admin. // *Action: Check that all environment variables are defined correctly // and that all configuration files exist in their correct places. / 04036, 00000, "CMCTL: error al leer de los ficheros de errores de Connection Manager" // *Cause: Problem while reading from Connection Manager or Connection Manager // Admin error files generated by the Connection Manager or Connection Manager // Admin when they have failed to start. // *Action: Check that a standard Network Error directory exists and that all // privileges on the directory are appropriate. / 04037, 00000, "CMCTL: error al abrir los ficheros de errores de Connection Manager" // *Cause: Failed to open Connection Manager or Connection Manager Admin // error files when they have failed to start. // *Action: Check that a Network Error directory exists and that all // privileges on the directory are appropriate. / 04038, 00000, "CMCTL: Formato de dirección o de cadena de comandos incorrecto" // *Cause: An unacceptable string was encountered while attempting // to send a message to either the Connection Manager or Connection Manager Admin. // The addresses provided for either the Connection Manager or Connection Manager // Admin may be incorrectly constructed. // *Action: Check all address strings in configuration file (TNSNAMES.ORA) // and assure that they are properly formed. // If all is correct, please contact Oracle Customer Support. / 04039, 00000, "CMCTL: error al originar un proceso" // *Cause: An error was encountered while spawning a process due to an // internal operating system dependent problem. Machine resources may be // limited. // *Action: Retry command. Check permissions on Connection Manager executables // (cmadmin, cmgw) and the current setting of the search path. If necessary, // terminate other applications to free up machine resources. If the error // persists, contact Oracle Customer Support. / 04040, 00000, "CMCTL: fallo al inicializar el contexto de rastreo- El proceso continúa" // *Cause: Problem while opening specified trace file because of errors in // CMAN.ORA or because the user has incorrect privileges, or the file does // not exist. // *Action: Check the privileges on the configuration files and ensure that // all of them exist in their proper locations. / 04041, 00000, "CMCTL: Connection Manager ya está en ejecución. Operación de arranque cancelada" // *Cause: There is a Connection Manager already running and listening on the same // addresses. // *Action: None; the Connection Manager is already running. / 04042, 00000, "CMCTL: Connection Manager Admin ya está en ejecución. Operación de arranque cancelada" // *Cause: There is a Connection Manager Admin already running and listening on // the same addresses. // *Action: None; the Connection Manager Admin is already running. / 04043, 00000, "El Connection Manager tiene conexiones activas. Do you still want to stop it (y/n)?" // *Cause: The Connection Manager that is being stopped has active connections going // through. This is the confirmation message. // *Action: Respond by pressing y or n. Answering y will cause the active // database connection to be dropped; this is not generally recommended. / 04044, 00000, "CMCTL: Debe tener un fichero CMAN.ORA para contactar con el Connection Manager" // *Cause: There was an attempt to contact a default Connection Manager // where there was no CMAN.ORA present in the correct // directory. // *Action: Create an CMAN.ORA file. // Make sure it is placed in the correct directory and includes the correct // name for the Connection Manager you wish to contact. / 04045, 00000, "CMCTL: No se ha podido contactar con el Connection Manager en la dirección" // *Cause: There was an attempt to contact a Connection Manager on a specific address // which is not responding. // *Action: Check that the Connection Manager is actually listening on that address. / 04046, 00000, "CMCTL: No se ha podido contactar con el Connection Manager Admin en la dirección" // *Cause: There was an attempt to contact a Connection Manager Admin on a specific // address which is not responding. // *Action: Check that the Connection Manager Admin is actually listening on that // address. / 04047, 00000, "CMCTL: No se ha podido crear la dirección IPC del Connection Manager Admin" // *Cause: There was an attempt to contact a Connection Manager Admin using the IPC // address which is not responding. // *Action: Check that the Connection Manager Admin is actually running. / 04060, 00000, "CMCTL: Comando incorrecto: sólo se puede usar el comando STATUS en el Connection Manager remoto" // *Cause: The user entered a command that does not exist, or the user // tried to make a request other than STATUS to a remote Connection Manager. // *Action: Check the Net8 Administrator's Guide for // a list of CMCTL commands or type HELP for a list of valid commands. / 04061, 00000, "CMCTL: Comando incorrecto o error de sintaxis: Debe especificar un nivel de rastreo" // *Cause: The user did not specify a trace level. // *Action: Specify a trace level and retry command. / 04062, 00000, "CMCTL: Comando incorrecto o error de sintaxis: Para obtener ayuda, escriba help/h/?" // *Cause: The user entered an invalid command. // *Action: Check the Net8 Administrator's Guide or type // HELP for a list of valid commands. / 04063, 00000, "CMCTL: Fallo al asignar memoria para buffers" // *Cause: CMCTL was unable to allocate memory for internal buffers. // *Action: Check the amount of available memory on your machine to ensure // that there is enough memory to run this executable. If necessary, free up // memory by running fewer programs, then try again. / 04064, 00000, "CMCTL: No se ha encontrado CMANAGER_NAME en CMAN.ORA" // *Cause: CMCTL was unable to find the CMANAGER_NAME parameter in CMAN.ORA. // *Action: Check that the CMAN.ORA file is properly constructed. / 04065, 00000, "CMCTL: El comando no se puede ejecutar de forma remota" // *Cause: A command other than status and version has been attempted // remotely. // *Action: If you desire execute any command other than status and version, // you must run CMCTL on the Connection Manager machine. / / The range 04070 to 04089 will be reserved for the help messages used by / CMCTL program / 04070, 00000, "sintaxis de CMCTL: [cmctl] [argumento]\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04071, 00000, " donde es uno de los siguientes: \n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04072, 00000, " * start - arrancar nombre_proceso\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04073, 00000, " * stop - parar nombre_proceso\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04074, 00000, " * status - obtiene el estado de process_name\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04075, 00000, " * stats - obtiene estadísticas de process_name\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04076, 00000, " * version - solicita el número de versión del programa de control CMCTL\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04077, 00000, " * exit - sale del programa de control CMCTL\n\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04078, 00000, " process_name es un proceso cman, cm o adm\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04079, 00000, " * cman - solicitará el Connection Manager (cman y adm)\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04080, 00000, " * cm - solicitará sólo el proceso Connection Manager\n " // *Cause: Help message displayed by CMCTL. // *Action: None. / 04081, 00000, " * adm - solicitará sólo el proceso Connection Manager Admin\n\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04082, 00000, " * log_on - solicita a process_name la conexión\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04083, 00000, " * log_off - solicita a process_name la desconexión\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04084, 00000, " * trace_on - solicita al nombre de proceso que active el rastreo\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04085, 00000, " NOTA: el usuario DEBE especificar un nivel de rastreo\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04086, 00000, " (USER o ADMIN) en el campo de argumento\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04087, 00000, " * trace_off - solicita al nombre de proceso que desactive el rastreo\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04088, 00000, " el argumento sólo se proporciona con el rastreo activado (trace_on)\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / 04089, 00000, " * para trace_on - el argumento se considera el nivel de rastreo\n\n" // *Cause: Help message displayed by CMCTL. // *Action: None. / /////////////////////////////////////////////////////////////////////////// / / 04201 - 04300 NU errors / /////////////////////////////////////////////////////////////////////////// / / The range 04201 to 04300 should be reserved for the NU component. / The messages will include status messages as well as error messages. / 04201, 00000, "ERROR de Sintaxis en el Asistente de Rastreo: Falta el nombre de fichero\n" // *Cause: Trace file name argument is missing // *Action: Put the trace file name as the last command line argument for // for this tool. / 04202, 00000, "ERROR de Sintaxis en el Asistente de Rastreo: Faltan argumentos \n" // *Cause: The and/or the arguments are missing // *Action: Put the right number of command line arguments. / 04203, 00000, "ERROR de Sintaxis en el Asistente de Rastreo: Opciones no válidas\n " // *Cause: The options provided are not valid // *Action: Check the valid options for this tool. / 04204, 00000, "ERROR Interno en el Asistente de Rastreo: No se ha podido abrir el fichero de rastreo\n" // *Cause: The trace file name given doesn't exist or it is not // accessible for this user. // *Action: Check the spelling, and permissions of the trace file. / 04205, 00000, "ERROR Interno en el Asistente de Rastreo: Memoria\n" // *Cause: Possible memory problem // *Action: Verify the amount of available memory on the system. / 04206, 00000, "ERROR Interno en el Asistente de Rastreo: Tipo de Paquete\n" // *Cause: The packet type read by trcAsst is not valid. // *Action: Verify that your trace file is not corrupted. If trace file // looks OK, with not strange characters in it, contact World // Wide Support and provide trace file to them. / 04207, 00000, "ERROR Interno en el Asistente de Rastreo: Longitud de Paquete\n" // *Cause: The packet being decode is corrupted. // *Action: Verify that your trace file is not corrupted. If trace file // looks OK, with not strange characters in it, contact World // Wide Support and provide trace file to them. / 04208, 00000, "ERROR Interno en el Asistente de Rastreo: Error Fatal\n" // *Cause: Fatal internal error // *Action: Contact World Wide Support. / 04209, 00000, "ERROR Interno en el Asistente de Rastreo: Tipo de Error \n" // *Cause: Internal type error, // *Action: Contact World Wide Support. / 04210, 00000, "ERROR Interno en el Asistente de Rastreo: Fin de fichero\n" // *Cause: Reaching End of File to soon. Not able to decode trace file. // Your trace file appears to be truncated. // *Action: Generate another trace file. This trace file can not be decoded. / 04211, 00000, "ERROR Interno en el Asistente de Rastreo: CORE\n" // *Cause: Internal System Error // *Action: Contact World Wide Support. / 04212, 00000, "ERROR Interno en el Asistente de Rastreo: Tipo de Error NACOM \n" // *Cause: Not able to decode Network Authentication information // *Action: Contact World Wide Support. / 04231, 00000, "AVISO del Asistente de Rastreo: Usando por defecto el formato Oracle Trace\n " // *Cause: This trace file may not be a Network trace file. The default // format (Oracle Trace) will be assumed. // *Action: None. / 04232, 00000, "AVISO del Asistente de Rastreo: No se han recuperado todas las filas\n" // *Cause: Trace Assitante won't retrieve all the rows data. // *Action: None. / 04233, 00000, "AVISO del Asistente de Rastreo: Se ha sobrepasado la longitud del paquete\n" // *Cause: Trying to read beyond packet length. The trace file may be // corrupted // *Action: None. / 04234, 00000, "AVISO del Asistente de Rastreo: no se puede descodificar TTC \n" // *Cause: Trace assistant does not have enough information to decode TTC // data. This maybe an old trace file or from a platform that // trace assistant does not understand. // *Action: None. / 04235, 00000, "AVISO del Asistente de Rastreo: protocolo TTC desconocido\n" // *Cause: Trace Assistant has reached a point in which the TTC protocol // can not be understood. // *Action: None. / /////////////////////////////////////////////////////////////////////////// / / ---------------------------- unassigned --------------------------------- / /////////////////////////////////////////////////////////////////////////// / Copyright (c) 1991, 1996, 1997 by the Oracle Corporation. All rights reserved. / / / $Header: net12150.msg 06-aug-97.15:13:07 tmlee Exp $ / / / NAME / net12150.msg - NETwork external message file starting from 12150 - / U.S. english version / / / FUNCTION / Network error message file, American English version. / / / NOTES / Only external errors are to be put into this file. Internal / messages are to put into netius.msg. / / This file, along with netius.msg and net12500.msg, forms tnsus.msg. As a / result, the errors in this file may not overlap with the errors in / those files. Otherwise, errors will result when generating tnsus.msb. / / Message text should be limited to a maximum of 76 characters. / Messages containing embedded % directives should not overrun / the 76 character limit unless they signal unusual errors / which do not occur as part of user applications. For example, / startup errors and system-dependent errors can probably get / away with longer message text. / / / '/' at beginning-of-line for comments. / '//' at beginning-of-line for *Cause: and *Action: fields. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////// Please maintain this map ////////////////////// / // 00001 - 04200 See netius.msg / . / . / 12150 - 12195 Reserved for OSN (Not to be used by TNS) / 12196 - 12285 NR errors reportable by OSN (returned by nricall()) / 12286 - 12499 ---(Reserved)--- / 12500 - 12699 See net12500.msg / . / . / . / /////////////////////////// Please maintain this map ////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / / / / OWNER / Network and Management Products - Server Technologies / / MODIFIED / tmlee 08/06/97 - modify 12204 / rwessman 03/16/97 - split from netus.msg to correct bug in building / oraus.msg. / 12150, 00000, "TNS:no se han podido enviar datos" // *Cause: Unable to send data. Connection probably disconnected. // *Action: Re-establish connection. If the error is persistent, turn // on tracing and reexecute the operation. / 12151, 00000, "TNS:el tipo de paquete recibido del nivel de red es incorrecto" // *Cause: Internal error. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12152, 00000, "TNS:no se ha podido enviar mensaje de ruptura" // *Cause: Unable to send break message. Connection probably disconnected. // *Action: Re-establish connection. If the error is persistent, turn // on tracing and reexecute the operation. / 12153, 00000, "TNS:no conectado" // *Cause: Not currently connected to a remote host. // *Action: Re-establish connection. / 12154, 00000, "TNS:no se ha podido resolver el nombre del servicio" // *Cause: The service name specified is not defined correctly in the // TNSNAMES.ORA file. // *Action: Make the following checks and correct the error: // - Verify that a TNSNAMES.ORA file exists and is in the proper // place and accessible. See the operating system specific manual // for details on the required name and location. // - Check to see that the service name exists in one of the // TNSNAMES.ORA files and add it if necessary. // - Make sure there are no syntax errors anywhere in the file. // Particularly look for unmatched parentheses or stray characters. // Any error in a TNSNAMES.ORA file makes it unusable. See // Chapter 4 in the SQL*Net V2 Administrator's Guide. If // possible, regenerate the configuration files using the Oracle // Network Manager. / 12155, 00000, "TNS:el tipo de datos recibido en el paquete NSWMARKER es incorrecto" // *Cause: Internal error during break handling. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12156, 00000, "TNS:se ha intentado reinicializar la línea desde un estado incorrecto" // *Cause: Internal error during break handling. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12157, 00000, "TNS:error interno de comunicación de la red" // *Cause: Internal error during network communication. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12158, 00000, "TNS:no se ha podido inicializar el subsistema de parámetros" // *Cause: Unable to locate parameter file. // *Action: Verify that a valid parameter file exists, and is readable. / 12159, 00000, "TNS:no se puede escribir en el fichero de rastreo" // *Cause: The trace file to be generated is not writeable by this user. // *Action: If the user does not have write permissions in the directory // to which the trace file will be written, contact the DBA to get the // proper permissions or use TRACE_DIRECTORY_CLIENT in SQLNET.ORA // to specify a directory the user can write to. / 12160, 00000, "TNS:error interno: número de error incorrecto" // *Cause: Corrupt error reporting subsystem. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12161, 00000, "TNS:error interno: recibidos datos parciales" // *Cause: The connection may be terminated. // *Action: Reconnect and try again. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12162, 00000, "TNS:nombre de servicio especificado incorrectamente" // *Cause: The connect descriptor corresponding to the service name in // TNSNAMES.ORA is incorrectly specified. // *Action: Make sure there are no syntax errors in the connect descriptor. // Particularly look for unmatched parentheses or stray characters. // Any error in a TNSNAMES.ORA file makes it unusable. See Chapter 4 // in the SQL*Net V2 Administrator's Guide. / 12163, 00000, "TNS:el descriptor de conexión es demasiado largo" // *Cause: The connect descriptor corresponding to the service name in // TNSNAMES.ORA is too long. // *Action: The maximum length for a connect descriptor is 512 bytes and this // limit has been exceeded. Use a smaller connect descriptor. If this is not // possible, contact Worldwide Customer Support. / 12164, 00000, "TNS:falta el fichero Sqlnet.fdf" // *Cause: The sqlnet.fdf file doesn't exist in $ORACLE_HOME/network/admin. // *Action: The sqlnet.fdf file is required for Oracle Tracing to occur. // Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or // turn off tracing in your ORA file. / 12165, 00000, "TNS:Intentando escribir el fichero de rastreo en el espacio de intercambio." // *Cause: Oracle Trace doesn't allow writing trace information into your // swap space. // *Action: Oracle Trace cannot write trace information into swap space // so either disable tracing or redirect trace files to be written to another // area of your disk. 12166, 00000, "TNS:El cliente no puede conectar con el agente HO." // *Cause: NVstring contained DESCRIPTION/HO. // *Action: Call HO agent from integrating server. / / This line is an OSN Magic Cookie. Don't eat it. Last OSN error in 2.0.9. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 12196 - 12285 NR errors reportable to OSN. / 12196, 00000, "TNS:se ha recibido un error de TNS" // *Cause: The navigation layer received an error from TNS. // *Action: See the error log file for the specific TNS error. / 12197, 00000, "TNS:error de resolución de palabra clave-valor" // *Cause: The navigation layer received an error while trying to look up a // value for a keyword. // *Action: Check the syntax of the connect descriptor. / 12198, 00000, "TNS:no se ha podido encontrar la ruta de acceso al destino" // *Cause: Could not navigate a path through Interchanges to the destination. // This error occurs if an invalid community is in the address string, or // the address includes a protocol that is not available or the // TNSNAV.ORA file does not have a correct CMANAGER address specified or // the Interchange is down. // *Action: Assure that Interchanges necessary to get to the desired // destination are up and have available capacity for an additional // connection. Also check that the correct community and protocol have been // specified in the CMANAGER address used. / 12200, 00000, "TNS:no se ha podido asignar memoria" // *Cause: Out of memory on machine. // *Action: Reconfigure machine to have more storage or run fewer applications // while the Interchange is running. / 12201, 00000, "TNS:el buffer de conexión es demasiado pequeño" // *Cause: TNS connection buffer supplied by the application was too small // to retrieve the data sent back. // *Action: Supply a larger connection buffer. If problem persists, call // Worldwide Customer Support. / 12202, 00000, "TNS:error interno de navegación" // *Cause: Internal navigation error. // *Action: Not normally visible to the user. For further details contact // Worldwide Customer Support. / 12203, 00000, "TNS:no se puede conectar con el destino" // *Cause: Invalid TNS address supplied or destination is not listening. // This error can also occur because of underlying network transport // problems. // *Action: Verify that the service name you entered on the command line // was correct. Ensure that the listener is running at the remote node and // that the ADDRESS parameters specified in TNSNAMES.ORA are correct. // Finally, check that all Interchanges needed to make the connection are // up and running. / 12204, 00000, "TNS:una aplicación ha rechazado los datos recibidos" // *Cause: The application using the Interchange or Connection Manager // refused the connection at the listener. // *Action: Make sure that the application listener at the destination is // functioning correctly. If it is and the problem persists, contact // Worldwide Customer Support. / 12205, 00000, "TNS:no se han podido obtener las direcciones fallidas" // *Cause: Internal navigation error. // *Action: Not normally visible to the user. For further details contact // Worldwide Customer Support. / 12206, 00000, "TNS:recibido un error de TNS durante la navegación" // *Cause: Internal navigation error because of an unexpected TNS error. // *Action: Look at the log file to find the TNS error. If necessary, turn // on tracing and repeat the operation. / 12207, 00000, "TNS:no se puede efectuar la navegación" // *Cause: Improperly configured navigation file TNSNAV.ORA. // *Action: Check the syntax of the TNSNAV.ORA file on the application`s // machine,and verify that it lists the correct communities. / 12208, 00000, "TNS:no se ha podido encontrar el fichero TNSNAV.ORA" // *Cause: Either the ORACLE environment is not set up correctly, or the // TNSNAV.ORA file is not present. // *Action: Ensure that the ORACLE environment is set up appropriately // on your platform and that a TNSNAV.ORA file is present. / 12209, 00000, "TNS:se ha encontrado una variable global no inicializada" // *Cause: Application calling navigation routine has not properly configured // the global variables. There are no TNSNAV.ORA files available, or they // are defective. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12210, 00000, "TNS:error al localizar datos del Navegador" // *Cause: Application calling navigation routine has not properly configured // the TNSNAV.ORA file. // *Action: Check the syntax of the TNSNAV.ORA file. / 12211, 00000, "TNS:necesita la entrada PREFERRED_CMANAGERS en TNSNAV.ORA" // *Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined. // *Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file. / 12212, 00000, "TNS:enlace PREFERRED_CMANAGERS incompleto en TNSNAV.ORA" // *Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file // does not have a CMANAGER_NAME specified. // *Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS // binding. Use of the Oracle Network Manager should eliminate this // error. / 12213, 00000, "TNS:enlace PREFERRED_CMANAGERS incompleto en TNSNAV.ORA" // *Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file // does not have an ADDRESS specified. // *Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. / 12214, 00000, "TNS:falta la entrada de comunidades locales en TNSNAV.ORA" // *Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA. // *Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA // file. / 12215, 00000, "TNS:direcciones de PREFERRED_NAVIGATORS mal definidas en TNSNAV.ORA" // *Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. // entry. // *Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA // / 12216, 00000, "TNS:direcciones de PREFERRED_CMANAGERS mal definidas en TNSNAV.ORA" // *Cause: Address binding for the PREFERRED_CMANAGERS entry in the client's // TNSNAV.ORA file is improperly entered. // *Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. / 12217, 00000, "TNS:no se ha podido contactar con PREFERRED_CMANAGERS en TNSNAV.ORA" // *Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or // addresses specified are wrong, or the intended Connection Managers are // unavailable. // *Action: Check the PREFERRED_CMANAGERS entries in the client's // TNSNAV.ORA file and correct them or talk with your network administrator // to determine if the specified Connection Managers are available. // Verify that the Interchangess are active by using the INTCTL STATUS // command. / 12218, 00000, "TNS:datos de configuración de la red no válidos" // *Cause: Poorly formed network configuration data. For example, a // PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the // client's TNSNAV.ORA file. Or an Interchange downtime parameter // (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA. // *Action: Check the entries in TNSNAV.ORA and the Interchange // configuration files and correct them. If necessary, talk with your // network administrator to determine if the specified Interchanges // (Connection Managers) are available and properly configured. // Use the Oracle Network Manager to generate the configuration files // if necessary. / 12219, 00000, "TNS:falta el nombre de comunidad de la dirección en ADDRESS_LIST" // *Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it // that have no COMMUNITY component and others that do have a COMMUNITY // component. // *Action: Check that in the connect descriptors you are using either // all the ADDRESSes have a COMMUNITY component or all do not. / / All succeeding errors are a remap of NS erros in NR / 12221, 00000, "TNS:parámetros de ADDRESS no válidos" // *Cause: An illegal set of protocol adapter parameters was specified. In // some cases, this error is returned when a connection cannot be made to the // protocol transport. // *Action: Verify that the destination can be reached using the specified // protocol. Check the parameters within the ADDRESS section of // TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the // Oracle operating system specific documentation for your platform. // Protocols that resolve names at the transport layer (such as DECnet object // names) are vulnerable to this error if not properly configured or names are // misspelled. / 12222, 00000, "TNS:no existe este adaptador de protocolo" // *Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" // keyword-value pair in a TNS address) is unknown. If the supplied address // is typographically correct then the protocol adaptor is not installed. // *Action: Install the protocol adapter or correct typographically error, // as appropriate. Note: if the supplied address was derived from // resolving the service name, check the address in the appropriate file // (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA). / 12223, 00000, "TNS:se ha excedido la restricción de límite interno" // *Cause: Too many TNS connections open simultaneously. // *Action: Wait for connections to close and re-try. / 12224, 00000, "TNS:no hay ningún listener" // *Cause: The connection request could not be completed because the listener // is not running. // *Action: Ensure that the supplied destination address matches one of // the addresses used by the listener - compare the TNSNAMES.ORA entry with // the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to // go by way of an Interchange). Start the listener on the remote machine. / 12225, 00000, "TNS:no se puede acceder al host destino" // *Cause: Contact can not be made with remote party. // *Action: Make sure the network driver is functioning and the network is up. / 12226, 00000, "TNS:se ha excedido la cuota de recursos del sistema operativo" // *Cause: The current user has exceeded the allotted resource assigned in the // operating system. // *Action: Acquire more operating system resource, or perform a different // function. / 12227, 00000, "TNS:error de sintaxis" // *Cause: The supplied connect descriptor contains illegal syntax. // *Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. / 12228, 00000, "TNS:el adaptador de protocolo no se puede cargar" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter is // missing or one of its supporting libraries is missing then this error is // returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will include the name of the shared library (or DLL) that // could not be loaded. / 12229, 00000, "TNS:el Intercambiador no tiene más conexiones libres" // *Cause: One or more Interchanges along the path to the destination // desired has no more free connections available to be used for this // call. // *Action: Try again later when the Interchanges are less busy, or contact // your network administrator to have him determine which interchange it is, // and increase the number of connections available on that interchange. / 12230, 00000, "TNS:se ha producido un error grave en la red al establecer esta conexión" // *Cause: This error is reported by an interchange which fails to make // contact with the destination due to a physical network error while calling // a destination. // *Action: Try again later when the network service may have been fixed // or report the problem to your Network Administrator so that he may fix // the problem. / 12231, 00000, "TNS:No se puede conectar con el destino" // *Cause: This error is reported by an interchange which fails to find a // possible connection along the path to the destination. // *Action: Report the problem to your Network Administrator so that he may // fix the problem. / 12232, 00000, "TNS:No hay ruta de acceso disponible hacia el destino" // *Cause: This error is reported by an interchange which fails to find a // possible path to the destination. // *Action: Report the problem to your Network Administrator so that he may // fix the problem. / 12233, 00000, "TNS:Fallo al aceptar la conexión" // *Cause: This error is reported by an interchange which fails to accept // a connection due to a redirect failure. // *Action: Report the problem to your Network Administrator so that he may // isolate the interchange problem. / 12234, 00000, "TNS:Redireccionr al destino" // *Cause: This error is reported by an interchange which determines that this // interchange is not the right gateway and needs to redirect the connection // to another gateway along the path to the destination. // *Action: None. / 12235, 00000, "TNS:Fallo al redireccionar al destino" // *Cause: This error is reported by an interchange which fails to redirect // a connection to another interchange along the path to the destination. // *Action: Report the problem to your Network Administrator so that he may // fix the problem. / 12236, 00000, "TNS:adaptador de protocolo no cargado" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter has not // been loaded, then this error is returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will have the name of the shared library (or DLL) that has // not been loaded. / / This line is an OSN Magic Cookie. Don't eat it. Last NR error in 2.0.9. / / / Copyright (c) 1991, 1996, 1997 by the Oracle Corporation. All rights reserved. / / / $Header: net12500.msg 07-may-97.23:53:11 emalasky Exp $ / / / NAME / net12500.msg - NETwork external message file starting from 12500 - / U.S. english version / / / FUNCTION / Network error message file, American English version. / / / NOTES / Only external errors are to be put into this file. Internal / messages are to put into netius.msg. / / This file, along with netius.msg and net12150.msg, forms tnsus.msg. As a / result, the errors in this file may not overlap with the errors in / those files. Otherwise, errors will result when generating tnsus.msb. / / Message text should be limited to a maximum of 76 characters. / Messages containing embedded % directives should not overrun / the 76 character limit unless they signal unusual errors / which do not occur as part of user applications. For example, / startup errors and system-dependent errors can probably get / away with longer message text. / / / '/' at beginning-of-line for comments. / '//' at beginning-of-line for *Cause: and *Action: fields. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////// Please maintain this map ////////////////////// / // 00001 - 04200 See netius.msg / . / . / 12150 - 12285 See net12150.msg / 12286 - 12499 ---(Reserved)--- / 12500 - 12530 NSG errors reportable by OSN (returned in cndo). / 12531 - 12629 NS (and NT errors reported as NS errors) reportable by OSN / 12630 - 12699 NA errors (returned by native services) / . / . / . / /////////////////////////// Please maintain this map ////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / / / / OWNER / Network and Management Products - Server Technologies / / MODIFIED / emalasky 05/07/97 - 12505: no args, better cause / emalasky 05/01/97 - rollback 12505 / smckinle 04/21/97 - Change 12505 to take an SID parameter. / rwessman 03/19/97 - Eliminated references to Secure Network Services. It / rwessman 03/09/97 - split from netus.msg to correct bug in building / oraus.msg. / / / 12500 - 12530 Reserved for NSG errors reportable to OSN. / / tnslsnr errors... 12500, 00000, "TNS:el listener no ha podido arrancar un proceso del servidor dedicado" // *Cause: The process of starting up a dedicated server process failed. // The executable could not be found or the environment may be set up // incorrectly. // *Action: Turn on tracing at the ADMIN level and reexecute the operation. // Verify that the ORACLE Server executable is present and has execute // permissions enabled. Ensure that the ORACLE environment is specified // correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being // called may not be installed on the local hard drive. Please check that // the correct Protocol Adapter are successfully linked. // If error persists, contact Oracle Customer Support. / 12501, 00000, "TNS:el listener no ha podido originar el proceso" // *Cause: The listener failed to start the program specified. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the alias of the program started by listener in the system // LISTENER.ORA file. Make sure the program exists and the arguments are // correct. // Do not include in error manual. / 12502, 00000, "TNS:el listener no ha recibido CONNECT_DATA del cliente" // *Cause: No CONNECT_DATA was passed to the listener. // *Action: Check that the service name resolved from TNSNAMES.ORA has // the CONNECT_DATA component of the connect descriptor. / 12504, 00000, "TNS:el listener no ha recibido el SID en CONNECT_DATA" // *Cause: The SID was missing from the CONNECT_DATA. // *Action: Check that the connect descriptor corresponding to the service // name in TNSNAMES.ORA has an SID component in the CONNECT_DATA. / 12505, 00000, "TNS:el receptor no ha podido resolver el SID proporcionado en el descriptor de conexión" // *Cause: The SID in the CONNECT_DATA was not found in the listener's tables. // *Action: Check to make sure that the SID specified is correct. // The SIDs that are currently registered with the listener can be obtained by // typing "LSNRCTL SERVICES ". These SIDs correspond to SID_NAMEs // in TNSNAMES.ORA, or db_names in INIT.ORA. // *Comment: This error will be returned if the database instance has not // registered with the listener; the instance may need to be started. / 12506, 00000, "TNS:el listener no ha recibido el ALIAS en CONNECT_DATA" // *Cause: The SID was missing from the CONNECT_DATA. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the command line or name-address mappings for the // ALIAS component of the CONNECT_DATA. // Do not include in error manual. / 12507, 00000, "TNS:el listener no ha podido resolver el ALIAS proporcionado" // *Cause: The ALIAS in CONNECT_DATA was not found in the system // TNSNAMES.ORA file. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check to make sure that the ALIAS specified is correct. // Do not include in error manual. / 12508, 00000, "TNS:el listener no ha podido resolver el COMANDO proporcionado" // *Cause: The COMMAND given to listener is not supported. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the COMMAND given to listener. This error is probably // caused by incompatible SQL*Net versions. // Do not include in error manual. / 12509, 00000, "TNS:el listener no ha podido redirigir el cliente al gestor de servicios" // *Cause: The dispatcher terminated unexpectedly // *Action: Attempt to connect again and if the same error occurs, // contact the DBA to check the state of the dispatchers for this SID. // If the problem persists, turn on tracing in the listener to determine // the TNS error caused by the redirect. / 12510, 00000, "TNS:la base de datos no tiene suficientes recursos para gestionar la solicitud de este SID" // *Cause: The dispatchers are busy handling other requests. // *Action: Contact the DBA to increase the number of dispatchers // servicing this SID. / 12511, 00000, "TNS:se ha encontrado el gestor de servicios, pero no acepta conexiones" // *Cause: The dispatchers are busy handling other requests and they notified // the listener that they are temporarily busy. // *Action: Attempt the connection again. If error persists, ask // the DBA to increase the number of dispatchers. / 12512, 00000, "TNS:se ha encontrado el gestor de servicios, pero no tiene ninguna dirección de redirección registrada" // *Cause: The dispatcher just came up and has not had time yet to register the // address that a client should be redirected to. // *Action: Attempt the connection again. If error persists, ask // the DBA to increase the number of dispatchers. / 12513, 00000, "TNS:se ha encontrado el gestor de servicios, pero está registrado en otro protocolo" // *Cause: The dispatchers registered for this service are connected to // the listener by way of a different network protocol than that of the client. // *Action: Contact the DBA to register a dispatcher on your protocol. / / This line is an OSN Magic Cookie. Don't eat it. Last NSG error in 2.0.9. / / //////////////////////////////////////////////////////////////////// / / 12531 - 12629 ns errors reportable to osn: / / 12531 - 15609 ns primary errors / 12610 - 12629 ns secondary errors / / A primary may (optionally) be qualified by a secondary / error. For example: 12531 ("invalid argument") might / be qualified by 12617 ("bad 'what' value"). / 12531, 00000, "TNS:no se puede asignar memoria" // *Cause: Sufficient memory could not be allocated to perform the desired // activity. // *Action: Either free some resource for TNS, or add more memory to the // machine. For further details, turn on tracing and reexecute the operation. / 12532, 00000, "TNS:argumento no válido" // *Cause: An internal function received an invalid parameter. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12533, 00000, "TNS:parámetros de ADDRESS no válidos" // *Cause: An illegal set of protocol adapter parameters was specified. In // some cases, this error is returned when a connection cannot be made to the // protocol transport. // *Action: Verify that the destination can be reached using the specified // protocol. Check the parameters within the ADDRESS section of // TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the // Oracle operating system specific documentation for your platform. // Protocols that resolve names at the transport layer (such as DECnet object // names) are vulnerable to this error if not properly configured or names are // misspelled. / 12534, 00000, "TNS:operación no soportada" // *Cause: An internal function received a request to perform an // operation that is not supported (on this machine). // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12535, 00000, "TNS:time out de la operación" // *Cause: The requested connection could not be completed within the timeout // period specified by the CONNECT_TIMEOUT parameter in listener.ora. This // error arises from the tnslsnr. // *Action: Either reconfigure CONNECT_TIMEOUT to be 0, which means // wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher // value. Or, if the timeout is unacceptably long, turn on tracing // for further information. / 12536, 00000, "TNS:la operación se bloquearía" // *Cause: An internal operation did not commence because to do so would // block the current process and the user has requested that operations be // non-blocking. // *Action: None needed; this is an information message. / 12537, 00000, "TNS:conexión cerrada" // *Cause: "End of file" condition has been reached; partner has disconnected. // *Action: None needed; this is an information message. / 12538, 00000, "TNS:no existe ese adaptador de protocolo" // *Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" // keyword-value pair in a TNS address) is unknown. If the supplied address // is typographically correct then the protocol adaptor is not installed. // *Action: Install the protocol adapter or correct typographically error, // as appropriate. Note: if the supplied address was derived from // resolving the service name, check the address in the appropriate file // (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA). / 12539, 00000, "TNS:límite inferior o superior del buffer excedido" // *Cause: Buffer too small for incoming data or too large for outgoing data. // *Action: This restriction (which is associated with CONNECT DATA) is not // normally visible to the user. For further details, turn on tracing and // reexecute the operation; contact Oracle Customer Support. / 12540, 00000, "TNS:restricción de límite interno excedida" // *Cause: Too many TNS connections open simultaneously. // *Action: Wait for connections to close and re-try. / 12541, 00000, "TNS:no hay ningún listener" // *Cause: The connection request could not be completed because the listener // is not running. // *Action: Ensure that the supplied destination address matches one of // the addresses used by the listener - compare the TNSNAMES.ORA entry with // the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to // go by way of an Interchange). Start the listener on the remote machine. / 12542, 00000, "TNS:dirección ya en uso" // *Cause: Specified listener address is already being used. // *Action: Start your listener with a unique address. / 12543, 00000, "TNS:no se puede acceder al host destino" // *Cause: Contact can not be made with remote party. // *Action: Make sure the network driver is functioning and the network is up. / 12544, 00000, "TNS:los contextos tienen diferentes funciones de espera/prueba" // *Cause: Two protocol adapters have conflicting wait/test functions. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12545, 00000, "La conexión ha fallado porque el host destino o el objeto no existen" // *Cause: The address specified is not valid, or the program being // connected to does not exist. // *Action: Ensure the ADDRESS parameters have been entered correctly; the // most likely incorrect parameter is the node name. Ensure that the // executable for the server exists (perhaps "oracle" is missing.) // If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the // host name to a numeric IP address and try again. / 12546, 00000, "TNS:permiso denegado" // *Cause: User has insufficient privileges to perform the requested operation. // *Action: Acquire necessary privileges and try again. / 12547, 00000, "TNS:contacto perdido" // *Cause: Partner has unexpectedly gone away, usually during process // startup. // *Action: Investigate partner application for abnormal termination. On an // Interchange, this can happen if the machine is overloaded. / 12548, 00000, "TNS:lectura o escritura incompletas" // *Cause: A data send or receive failed. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12549, 00000, "TNS:cuota de recursos del sistema operativo excedida" // *Cause: The current user has exceeded the allotted resource assigned in the // operating system. // *Action: Acquire more operating system resource, or perform a different // function. / 12550, 00000, "TNS:error de sintaxis" // *Cause: The supplied connect descriptor contains illegal syntax. // *Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. / 12551, 00000, "TNS:falta palabra clave" // *Cause: The supplied connect descriptor is missing one or more TNS // keywords. // *Action: Check the syntax, and ensure all required keywords are present. / 12552, 00000, "TNS:la operación se ha interrumpido" // *Cause: An internal operation was interrupted and could not complete. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12554, 00000, "TNS:la operación actual todavía se está procesando" // *Cause: An internal operation is still in progress. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12555, 00000, "TNS:permiso denegado" // *Cause: User has insufficient privileges to perform the requested operation. // *Action: Acquire necessary privileges and try again. / 12556, 00000, "TNS:no hay ningún emisor" // *Cause: TNS detected an incoming connect request but there was no caller. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12557, 00000, "TNS:no se puede cargar el adaptador de protocolo" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter is // missing or one of its supporting libraries is missing then this error is // returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will include the name of the shared library (or DLL) that // could not be loaded. / 12558, 00000, "TNS:adaptador de protocolo no cargado" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter has not // been loaded, then this error is returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will have the name of the shared library (or DLL) that has // not been loaded. / 12560, 00000, "TNS:error del adaptador de protocolo" // *Cause: A generic protocol adapter error occurred. // *Action: Check addresses used for proper protocol specification. Before // reporting this error, look at the error stack and check for lower level // transport errors.For further details, turn on tracing and reexecute the // operation. Turn off tracing when the operation is complete. / 12561, 00000, "TNS:error desconocido" // *Cause: A generic protocol error occurred. // *Action: For further details, turn on tracing and reexecute the operation. / 12562, 00000, "TNS:manejador global erróneo" // *Cause: Internal error - bad 'gbh' agrument passed to TNS from caller. // System may have been linked with old libraries. // *Action: Not normally visible to the user, contact Oracle Customer // Support. / 12564, 00000, "TNS:conexión rechazada" // *Cause: The connect request was denied by the remote user (or TNS software). // *Action: Not normally visible to the user. For further details, turn on // tracing and reexecute the operation. / 12566, 00000, "TNS:error de protocolo" // *Cause: An unexpected TNS protocol error has occurred. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 12569, 00000, "TNS:fallo del total de control del paquete" // *Cause: The data received is not the same as the data sent. // *Action: Attempt the transaction again. If the error is persistent, turn // on tracing and reexecute the operation. / 12570, 00000, "TNS:fallo en el lector del paquete" // *Cause: An error occurred during a data receive. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12571, 00000, "TNS:fallo en el escritor del paquete" // *Cause: An error occurred during a data send. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12574, 00000, "TNS:redirección denegada" // *Cause: The connect request failed because it would have required // redirection and the caller has requested no redirections. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12582, 00000, "TNS:operación no válida" // *Cause: An internal function received an invalid request. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12583, 00000, "TNS:no hay ningún lector" // *Cause: A send operation has been requested but partner has already // disconnected. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12585, 00000, "TNS:datos truncados" // *Cause: A receive operation has completed with insufficient data // to satisfy the user's request. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12589, 00000, "TNS:no se puede transmitir la conexión" // *Cause: An attempt to hand-off a connection from one process to another // has failed because the protocol provider does not support it. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12590, 00000, "TNS:no hay ningún buffer de E/S" // *Cause: An attempt to perform an I/O operation failed because no buffer // was available. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12591, 00000, "TNS:fallo en la señal de evento" // *Cause: The TNS software is unable to signal an event occurrence. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 12592, 00000, "TNS:paquete en mal estado" // *Cause: An ill-formed packet has been detected by the TNS software. // *Action: For further details, turn on tracing and reexecute the // operation. If error persists, contact Oracle Customer Support. / 12593, 00000, "TNS:no hay ninguna conexión registrada" // *Cause: An attempt to solicit network event activity has failed because // no connections are registered for event notification. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12595, 00000, "TNS:no hay confirmación" // *Cause: TNS is unable to get requested confirmation acknowledgement from // remote partner. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12596, 00000, "TNS:inconsistencia interna" // *Cause: TNS has detected an internal inconsistency. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12597, 00000, "TNS:el descriptor de conexión ya está en uso" // *Cause: Internal error - illegal use of connect descriptor. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12598, 00000, "TNS:el registro de la carátula ha fallado" // *Cause: The registration of a product banner with the Oracle server failed. // *Action: This is an error which is not normally visible externally. Enable // tracing and attempt to repeat the error. If it occurs // again, contact Oracle Customer Support. / 12599, 00000, "TNS:el total de control criptográfico no coincide" // *Cause: The data received is not the same as the data sent. // *Action: Attempt the transaction again. If error persists, check // (and correct) the integrity of your physical connection. / 12600, 00000, "TNS: fallo de apertura de la cadena" // *Cause: The creation of a string in ORACLE NLS format failed. // *Action: This is an internal error, enable tracing and attempt to repeat the // error. If it occurs again, contact Oracle Customer Support. / 12601, 00000, "TNS:fallo de comprobación de indicadores de información" // *Cause: The TNS information flags set by the process prior to connection // negotiation were not present after the negotiation was // finished. // *Action: This is an internal error. Enable tracing and attempt to repeat the // error. If it occurs again, contact Oracle Customer // Support. / / 12610 - 12629 ns secondary errors / /12611, 00000, "TNS:operation is not portable" // *Cause: Attempted operation is not portable. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / /12612, 00000, "TNS:connection is busy" // *Cause: Attempted operation failed because it conflicts with an on-going // action or status of the connection. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / /12615, 00000, "TNS:preempt error" // *Cause: A request to service an event failed because no event notification // has yet been posted. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12616, 00000, "TNS:no hay ninguna señal de evento" // *Cause: The TNS software is unable to enable event signals. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / /12617, 00000, "TNS:bad 'what' type" // *Cause: The operation failed because the type of data specified is unknown. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. Iferror persists, contact // Oracle Customer Support. / 12618, 00000, "TNS:las versiones son incompatibles" // *Cause: The two machines are running incompatible versions of TNS. // *Action: Check the version numbers, and upgrade the machine with the // smaller one. / 12619, 00000, "TNS:no se puede otorgar el servicio solicitado" // *Cause: The connect request failed because requested service could not be // provided by the local TNS software. // *Action: If appropriate, reexecute with reduced service requirements. / 12620, 00000, "TNS:la característica solicitada no está disponible" // *Cause: The connect request failed because a requested transport // characteristic could not be supported by the remote TNS software. // *Action: If appropriate, reexecute with reduced requirements. / 12622, 00000, "TNS:las notificaciones de eventos no son homogéneas" // *Cause: An attempt to register a connection for event notification failed // because the event notification type conflicts with existing registrations. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12623, 00000, "TNS:la operación no es válida en este estado" // *Cause: Connection is half-duplex and a full-duplex operation was // attempted. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12624, 00000, "TNS:la conexión ya está registrada" // *Cause: An attempt to register a connection for event notification failed // because the connection is already registered. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12625, 00000, "TNS:falta un argumento" // *Cause: An operation failed because an argument was missing" // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12626, 00000, "TNS:tipo de evento incorrecto" // *Cause: An attempt to register a connection for event notification failed // because the event type is unknown. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12628, 00000, "TNS:no hay repeticiones de llamadas de eventos" // *Cause: An attempt to register a connection for event notification failed // because asynchronous callbacks are not available. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12629, 00000, "TNS:no hay ninguna prueba de evento" // *Cause: An attempt to register a connection for event notification failed // because the ability to test for events is not available. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / / 12630 - 12699 Reserved for NA errors. / 12630, 00000, "Operación de servicio nativo no soportada" // *Cause: An operation requested by a user is not supported by the native // services component. // *Action: This may be an internal error if the operation should have been // supported. / 12631, 00000, "Fallo al recuperar el nombre de usuario" // *Cause: The authentication service failed to retrieve the name of a user. // *Action: Enable tracing to determine which routine is failing. / 12632, 00000, "Fallo al buscar el rol" // *Cause: The authentication service failed to retrieve one of the user's // roles. // *Action: Enable tracing to determine which routine is failing. / 12633, 00000, "No hay servicios de verificación compartidos" // *Cause: The list of authentication services specified by the user does not // match those supported by the process. // *Action: Either specify another list or relink the executable with the // desired services. / 12634, 00000, "Fallo de asignación de memoria" // *Cause: Process was unable to allocate memory. // *Action: Terminate other processes in order to reclaim needed memory. / 12635, 00000, "No hay adaptadores de verificación disponibles" // *Cause: The executable was not linked with any authentication service // adapters but the sqlnet.ora parameter that determines whether or // not authentication is required was set to true. // *Action: Either disable the parameter or relink the executable with service // adapters. / 12636, 00000, "Fallo al enviar el paquete" // *Cause: A process was unable to send a packet to another process. // Possible causes are: // 1. The other process was terminated. // 2. The machine on which the other process is running went down. // 3. Some other communications error occurred. // *Action: If the cause is not obvious, contact Oracle Customer Support. / 12637, 00000, "Fallo al recibir el paquete" // *Cause: A process was unable to receive a packet from another process. // Possible causes are: // 1. The other process was terminated. // 2. The machine on which the other process is running went down. // 3. Some other communications error occurred. // *Action: If the cause is not obvious, contact Oracle Customer Support. / 12638, 00000, "Fallo al recuperar los credenciales" // *Cause: The authentication service failed to retrieve the credentials of a // user. // *Action: Enable tracing to determine the exact error. / 12639, 00000, "Fallo en la negociación del servicio de verificación" // *Cause: No match was found between the types of authentication services // that the client supports and those that the server is using. // *Action: Possible solutions: // 1. Change the entry in sqlnet.ora that determines which services // are to be used. // 2. Relink the client with at least one of the authentication // service adapters that the server supports. // 3. Relink the server with at least one of the authentication // service adapters that the client supports. // 4. Disable authentication on both the client and server. / 12640, 00000, "Fallo en la inicialización del adaptador de verificación" // *Cause: The function specified in the authentication table entry for the // service failed. // *Action: Enable tracing to determine the exact error. / 12641, 00000, "Fallo del servicio de verificación al inicializar" // *Cause: The authentication service failed during initialization. // *Action: Enable tracing to determine the exact error. / 12642, 00000, "No hay ninguna clave de sesión" // *Cause: A process has no session key associated with it because the // authentication service being used does not use one. // *Action: If a session key is required, use another authentication service. / 12643, 00000, "El cliente ha recibido un error interno del servidor" // *Cause: The client process received an error from the server that indicated // that an internal SQL*Net native services error had occurred. // *Action: Enable tracing on both processes and attempt to recreate the // problem. If successful in recreating the problem, contact Oracle // Customer Support. / 12644, 00000, "Fallo en la inicialización del servicio de verificación" // *Cause: The routine called to initialize the authentication adapter failed. // *Action: Enable tracing to determine the exact error. A likely cause is that // memory is exhausted. / 12645, 00000, "El parámetro no existe." // *Cause: A sqlnet.ora parameter from which a value was needed does not // exist. // *Action: Set the parameter in the parameter file. / 12646, 00000, "Valor incorrecto especificado para el parámetro booleano" // *Cause: The value specified for a parameter was set to a value other than // true/false or on/off. // *Action: Correct the value of the parameter. / 12647, 00000, "Verificación necesaria" // *Cause: The parameter that controls whether authentication is required was // set to true, but the executable does not have an // authentication service linked in. // *Action: Either re-link the executable with an authentication service // adapter or disable the parameter. / 12648, 00000, "La lista de algoritmos de cifrado o integridad de datos está vacía" // *Cause: A SQL*Net list-of-algorithms parameter was empty, e.g. // "()". // *Action: Change the list to contain the name of at least one // installed algorithm, or remove the list entirely if every // installed algorithm is acceptable. / 12649, 00000, "Algoritmo de cifrado o de integridad de datos desconocido" // *Cause: A SQL*Net list-of-algorithms parameter included an // algorithm name that was not recognized. // *Action: Either remove that algorithm name, correct it if it was // misspelled, or install the driver for the missing // algorithm. / 12650, 00000, "No es un algoritmo de cifrado o de integridad de datos común" // *Cause: The client and server have no algorithm in common for // either encryption or data integrity or both. // *Action: Choose sets of algorithms that overlap. In other words, // add one of the client's algorithm choices to the server's // list or vice versa. / 12651, 00000, "Algoritmo de cifrado o de integridad de datos inaceptable" // *Cause: The algorithm the server chose to use for encryption or // data integrity was not one of the choices acceptable to // the client. This is either the result of an internal // error, of a network data transmission error, or of // deliberate tampering with the transmitted data. // *Action: For further details, turn on tracing, re-execute the // operation, and contact Oracle Customer Support. / 12652, 00000, "Cadena truncada" // *Cause: Not enough memory was allocated for a string so it had to be // trucated // *Action: If it is OK that the string is truncated, then it is not an // error. Otherwise, call the routine that reported the error // again with a larger string buffer. / 12653, 00000, "Fallo de la función de control de verificación" // *Cause: The control function utilized by the authentication service driver // failed. // *Action: Enable tracing to determine the exact error. / 12654, 00000, "Fallo en la conversión de verificación" // *Cause: The authentication service was unable to convert the credentials // of a user from the format specific to the format into the // ORACLE format. // *Action: Enable tracing to determine the exact error. / 12655, 00000, "Fallo en la comprobación de la clave" // *Cause: The authentication service being used was unable to verify the // provided password. // *Action: Enable tracing to determine the exact error. / 12656, 00000, "El total de control criptográfico no coincide" // *Cause: The cryptographic checksum received with a packet of // incoming data didn't match the checksum computed by the // receiving end. This indicates that the packet was // tampered with or otherwise corrupted in transit. // *Action: Look for sources of data corruption, perhaps including // deliberate tampering. / 12657, 00000, "No hay algoritmos instalados" // *Cause: The near side of the connection required the use of a // service (either encryption or checksumming) when no // algorithms for that service were installed. // *Action: Remove the "ON" requirement for that service. / 12658, 00000, "Es necesario el servicio ANO, pero la versión TNS no es compatible" // *Cause: A client process that is running an earlier version of TNS // attempted toconnect but the connection failed because the server // process required that an ANO service (authentication, encryption, // etc.) be used. // *Action: Relink the calling executable and retry the connection or eliminate // the requirement that the service be used on the server side. / 12659, 00000, "Se ha recibido un error de otro proceso" // *Cause: An error was received by one or more services from the process on // the other side of the connection. // *Action: Enable tracing to determine the exact error(s). // The error(s) is (are) not returned directly because an error // generated by a server may not make sense on the client side and // vice-versa. / 12660, 00000, "Parámetros de cifrado o cifradototal de control no compatibles" // *Cause: One side of the connection specified "REQUIRED" for encryption // or crypto-checksumming, while the other side specified "REJECTED". // *Action: Change the "REQUIRED" side to "REQUESTED" if the // you want encryption or crypto-checksumming to be optional, or // change the "REJECTED" side to "ACCEPTED" if you do not // want the service to be optional. / 12661, 00000, "Verificación de protocolo a utilizar" // *Cause: The SQL*Net authentication service has determined that the SQL*Net // transport protocol in use is to be utilized to authenticate a // user's identity. // *Action: This error is used solely to communicate information between the // authentication service and the SQL*Net session layer and should not // be visible to the user. // If the error is seen, contact Oracle customer support. / 12662, 00000, "Fallo al recuperar el ticket proxy" // *Cause: The authentication adapter used by SQL*Net failed to retrieve the // credentials needed to authenticate a database link. // *Action: Enable tracing to determine the exact error. / 12663, 00000, "Los servicios solicitados por el cliente no están disponibles en el servidor" // *Cause: Service(s) that was (were) required by the client process were not // available on the server process. // *Action: Configure the server with the services required by the client (best // solution) or delete the requirement from the configuration // file of the client (least secure). / 12664, 00000, "Los servicios solicitados por el servidor no están disponibles en el cliente" // *Cause: Service(s) that was (were) required by the server process were not // available on the client process. // *Action: Configure the client with the services required by the server (best // solution) or delete the requirement from the configuration // file of the server (least secure). / 12665, 00000, "Fallo al abrir la cadena NLS" // *Cause: A native service was unable to make a string available for use by // the National Language Support component. // *Action: Make sure the National Language Support component has been // properly. If it has, enable tracing and report the problem // to Customer Support. / 12666, 00000, "Servidor dedicado: protocolo de transporte de salida distinto del de entrada" // *Cause: The protocol specified for an externally-identified outbound // connection from a dedicated server (database link) was not the same // as that used for the inbound connection. It is not possible for // SQL*Net to authenticate a proxy connection that uses a protocol // that is different from that which was used for the connection to // the dedicated server. // *Action: Specify the same protocol in the SQL*Net connect string or alias // for the outbound connection as that used for the inbound // connection / 12667, 00000, "Servidor compartido: protocolo de transporte de salida distinto del de entrada" // *Cause: The protocol specified for an externally-identified outbound // connection from a shared server (database link) was not the same as // as that used for the inbound connection. It is not possible for // SQL*Net to authenticate a proxy connection that uses a protocol // that is different from that which was used for the connection to // the shared server. // *Action: Specify the same protocol in the SQL*Net connect string or alias // for the outbound connection as that used for the inbound // connection / 12668, 00000, "Servidor dedicado: el protocolo de salida no soporta \"proxies\"" // *Cause: The protocol specified to perform an externally-identified proxy // connection (database link) from a dedicated server does // not support proxy connections. // *Action: Specify a protocol in the SQL*Net connect string or alias used for // the connection that does support externally-authenticated proxy // connections. // NOTE: Because of a limitation in SQL*Net, the protocol used for // the proxy connection must the same as that used for the // connection from the client to the server. / 12669, 00000, "Servidor compartido: el protocolo de salida no soporta \"proxies\"" // *Cause: The protocol specified to perform an externally-identified proxy // connection (database link) from a shared server does not support // proxy connections. // *Action: Specify a protocol in the SQL*Net connect string or alias used for // the connection that does support externally-authenticated proxy // connections. // NOTE: Because of a limitation in SQL*Net, the protocol used for // the proxy connection must the same as that used for the // connection from the client to the server. / 12670, 00000, "Clave de rol incorrecta" // *Cause: A password supplied for a role could not be validated by the // authentication service. // *Action: Supply the correct password. / 12671, 00000, "Servidor compartido: fallo del adaptador al guardar el contexto" // *Cause: The adapter for the authentication service failed when it tried to // save the data needed for proxy connections (database // links) through the multi-threaded server. // *Action: Enable tracing to determine the exact error. Contact Oracle // Customer Support if the reason is not obvious. / 12672, 00000, "Fallo de conexión a la base de datos" // *Cause: The authentication service adapter in use encountered an error // it attempted to validate the logon attempt of a user. // *Action: Enable tracing to determine the exact error encountered by the // adapter. / 12673, 00000, "Servidor dedicado: contexto no guardado" // *Cause: A connection was marked as being a proxy connection (database link) // from a dedicated server but no inbound context was present. // *Action: This error should not normally be visible to the user. Contact // Oracle Customer Support. / 12674, 00000, "Servidor compartido: contexto proxy no guardado" // *Cause: A connection was marked as being a proxy connection (database link) // from a shared server but no inbound context was present. // *Action: This error should not normally be visible to the user. Contact // Oracle Customer Support. / 12675, 00000, "Aún no está disponible el nombre de usuario externo" // *Cause: The authentication service in use was not able to return the // external name of a user of the ORACLE server because it is not // available to the service yet. // *Action: This is just an informational message and should not normally be // visible to the user. If the error does appear, contact Oracle // Customer Support. / 12676, 00000, "El servidor ha recibido un error interno del cliente" // *Cause: The server process received an error from the client which // indicated that an internal SQL*Net native services error had // occurred. // *Action: Enable tracing on both processes and attempt to recreate the // problem. If the problem recurs, contact Oracle Customer // Support. / 12677, 00000, "Servicio de verificación no soportado por el enlace de base de datos" // *Cause: The authentication service used by the proxy process (database // link) was unable to find the adapter being used by the client // in its list of authentication mechanisms. // *Action: Specify an authentication adapter that is shared by the client and // the server being used for the database link. / 12678, 00000, "La verificación está desactivada pero es necesaria" // *Cause: The configuration parameters that control whether SQL*Net // authentication is disabled or required were both set to TRUE. // *Action: Set one or both of the parameters to FALSE. / 12679, 00000, "Otro proceso ha desactivado los servicios nativos pero son necesarios" // *Cause: The remote process has disabled native services but the local // process requires them. // *Action: Enable native services on the remote process or disable them // locally. / 12680, 00000, "Los servicios nativos están desactivados pero son necesrios" // *Cause: The process has disabled native services but at least one service // is required. // *Action: Enable native services or change the configuration file so that // none of the available services are required. / 12681, 00000, "Fallo de conexión: la tarjeta SecurID todavía no tiene ningún código de pin" // *Cause: The SecurID card that is used to logon to Oracle, does not have // a pincode assigned to it. // *Action: Use one of the programs supplied by Security Dynamics to assign // a pincode to the card. / 12682, 00000, "Fallo de conexión: la tarjeta SecurID está en el siguiente modo PRN" // *Cause: The SecurID card and the SecurID server are out of sync and the // server requires the next cardcode to resynchronize the card. // *Action: Use one of the programs supplied by Security Dynamics to // resynchronize the SecurID card. / 12683, 00000, "cifrado/total de control criptográfico: ninguna preselección Diffie-Hellman" // *Cause: The "sqlnet.crypto_seed" parameter is missing from the // SQLNET.ORA parameters file for SQL*Net. // *Action: Add this line to SQLNET.ORA: // sqlnet.crypto_seed = "randomly-chosen text" / 12684, 00000, "cifrado/total de control criptográfico: preselección Diffie-Hellman demasiado pequeña" // *Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA // parameter file for SQL*Net is too small. // *Action: Add more randomly-chosen text to it, perhaps using Network // Manager. / 12685, 00000, "Servicio nativo necesario en modo remoto pero desactivado localmente" // *Cause: A native service is required by the remote process but native // services have been disabled locally. // *Action: Enable native services locally or change the configuration // parameters on the remote host so that no native services are // required. / 12686, 00000, "Comando no válido especificado para un servicio" // *Cause: An operation which does not exist was specified for a native // service. // *Action: This is a programming error and should not normally be visible to // the user. If the error does appear, contact Oracle Customer // Support. / 12687, 00000, "Fallo en el enlace de base de datos: han vencido las credenciales" // *Cause: The credentials that are used to authenticate the user for the // requested database link have expired. // *Action: Renew your credentials. Refer to the documentation specific for // your Network Authentication Adapter on how to do this. / 12688, 00000, "Fallo de conexión: el servidor SecurID ha rechazado el nuevo identificador" // *Cause: There are a number of reasons why the SecurID server would refuse // a pincode: // - The user might not have permission to make up his own pincode. // - The pincode was either too short or too long. Valid pincodes // consist of minimal four, but no more than eight characters. // - The pincode contains any non alpha-numeric characters. // *Action: Reexecute the operation and make sure to use a pincode that // satisfies the above requirements. If the problem persists, turn // on tracing at the Oracle Server side of the connection and // examine the trace file for the exact error. / 12689, 00000, "Es necesaria la verificación del servidor, pero no está soportada" // *Cause: Server Authentication is required for this connection, but not // supported by both sides of the connection. // *Action: Make sure both sides of the connection have the correct version of // Advanced Networking Option, and that the Authentication Adapter // supports Server Authentication. / 12690, 00000, "Fallo en la verificación del servidor, conexión cancelada" // *Cause: Server Authentication is required, but the server's credentials // were found invalid by the client. // *Action: Make sure that the server has a valid set of credentials. Refer to // your authentication adapter specific documentation on how to do // this. / 12699, 00000, "Error interno del servicio nativo" // *Cause: An internal error occurred in the native services component. // *Action: Enable tracing to determine the exact error. Contact Oracle // Customer Support. / / / This line is an OSN Magic Cookie. Don't eat it. / All new error messages up to 12699 ___MUST___ be placed in this file / above and before and preceding the preceding Magic Cookie line. / / This line is an OSN Magic Cookie. Don't eat it. Last NS error in 2.0.9. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 12700 - 12999: Reserved. / /////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////////////////////////////