Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML KM-Dim9:11950-DBA_CANT_GET_TABLESPACES Unable to determine the default and temporary tablespaces.
KM-Dim9:11950-DBA_CANT_GET_ TABLESPACES Unable to determine the default and temporary tablespaces .
CMS-XML Dim 12.2.1: SQL-25153(01B30B60) ORA-25153: Temporary Tablespace is Empty - message generated during "upgrade all"
Dim 12.2.1: SQL-25153(01B30B60) ORA-25153: Temporary Tablespace is Empty - message generated during "upgrade all"
CMS-XML KM-Dim10: After importing database cannot see change docs in any client get error: SQL-0438(1dbc38) ORA-25153: Temporary Tablespace is Empty
KM-Dim10: After importing database cannot see change docs in any client get error: SQL-0438(1dbc38) ORA-25153: Temporary Tablespace is Empty
CMS-XML Deployment marked as successful even though Oracle temporary tablespace ran out and some database updates did not occur
Deployment marked as successful even though Oracle temporary tablespace ran out and some database updates did not occur
CMS-XML TRK: ERR:ORA-03212 Temporary Segment cannot be created in locally-managed tablespace
Action: Alter temporary tablespace of user to a temporary tablespace or a dictionary-managed permanent tablespace . Cause: An attempt was made to create a temporary segment for SORT/HASH/LOBS in a locally-managed permanent tablespace.
CMS-XML KM-Dim9: Rebuilding Indexes, get: ORA-01630: max # extents (121) reached in temp segment in tablespace PCMS_TEMP
Correct by changing default storage parameters on temporary tablespace .
CMS-XML KM-Dim9: Error: ORA-01630: max # extents reached in temp segment for tablespace
PROBLEM 1: The user's Oracle account is referencing the wrong tablespace as temporary tablespace Background
CMS-XML Dim 10: ORA-01652: Unable to extend temp segment in tablespace PCMS_DATA
There will need to be at least this much contiguous free space in the PCMS_DATA tablespace, plus a 10% margin. If there is insufficient space, then the data file needs to be resized appropriately. This change may be temporary , as the data file can be sized down after the upgrade to recover available free space.
CMS-XML KM-Dim9: ORA-1652 Unable to extend temp segment by 512 in tablespace pcms_temp" occurs
KM-Dim9: ORA-1652 Unable to extend temp segment by 512 in tablespace pcms_temp" occurs
CMS-XML KM-Dim9: TBO error:ORA-1652 Unable to extend temp segment by 512 in tablespace pcms_temp
where nnn is the integer (in megabytes). More temp files can also be added if needed. After action completes the tablespace can be resized by dropping / readding the datafile(s).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs