This is the solution for the following problem:The topology relationship information table (xxx_RELATION$) did not have the matching partition corresponding to the feature table.

This is a brief information taken from Oracle documentation, where you can find a proposed solution for Oracle error: OCI-19207. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.

This is the solution for the following problem:TABLESPACE_NUMBER clause was specified more than once for an table, index or an index partition

Read this article if you found a ORA-64116 error in you logs. This article is dedicated especially for Oracle 11g Release 2 (11.2) but it can be useful for other Oracle Database releases.

This is the solution for the following problem:The length of the SDO_CODE column in the <layer>_SDOINDEX table could not be determined.

This is the solution for the following problem:Extending an index subpartition violated MAXSIZE limit.

In htis article you will fine a solution for error: The specified value must be a positive integer.. This solution is suitable for Oracle 11g Release 2 (11.2).

In this article you will be presented a brief description for error ORA-31501.

This is the solution for the following problem:Supplemental logging was not turned on while there was a logical standby database in the configuration. This could happen either on the primary database or on the logical standby database that was being switched over to be the primary database.

This is a brief information taken from Oracle documentation, where you can find a proposed solution for Oracle error: ORA-16701. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.

This is the solution suitable for Oracle 11g Release 2 (11.2) for the following problem:An attempt was made to run a second instance of I/O Calibration

This is the solution for the following problem:An attempt was made to analyze the performance of a SQL workload using two executions that were generated using two different

This is the solution for the following problem:Both the magic and version numbers failed to write. This usually occurs because disk space has been exhausted.

This is the solution for the following problem:An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for table name and/or column name.

In this short article you will be presented a quick solution for error DIA-48400.

This is a brief information taken from Oracle documentation, where you can find a proposed solution for Oracle error: ORA-48192. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.

Read this article if you found a ORA-02821 error in you logs. This article is dedicated especially for Oracle 11g Release 2 (11.2) but it can be useful for other Oracle Database releases.

This is the solution suitable for Oracle 11g Release 2 (11.2) for the following problem:Username may be too long

This is the solution for the following problem:The object being requested does not exists

In this short article you will be presented a quick solution for error ORA-38959.