Oracle - Errores y soluciones
Ratio: 4 / 5
ORA-00918: column ambiguously defined.
Cause: A column name used in a join exists in more than one table and is thus referenced ambiguously. In a join, any column name that occurs in more than one of the tables must be prefixed by its table name when referenced. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if tables EMP and DEPT are being joined and both contain the column DEPTNO, then all references to DEPTNO should be prefixed with the table name, as in EMP.DEPTNO or E.DEPTNO.
Action: Prefix references to column names that exist in multiple tables with either the table name or a table alias and a period (.), as in the examples above.
Ratio: 4 / 5
ORA-01090: shutdown in progress - connection is not permitted.
Ratio: 4 / 5
ORA-00057: maximum number of temporary table locks exceeded.
Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.
Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.
Ratio: 4 / 5
ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)
Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.
Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.
Ratio: 4 / 5
ORA-02068: following severe error from stringstring.
Cause: A severe error (disconnect, fatal Oracle error) received from the indicated database link. See following error text.
Action: Contact the remote system administrator.
- Está aquí:
-
Inicio
-
Bases de Datos
- Oracle Errores y Soluciones
