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: ORA-01552: cannot use system rollback segment for non-system tablespace 'PCMS_RBS' during a system import
KM-Dim9: ORA-01552: cannot use system rollback segment for non-system tablespace ' PCMS_RBS ' during a system import
CMS-XML DIM14: Documentation: Windows Installation Guide,Page 73, and Oracle tablespaces
To support the installation of a Dimensions CM 14.1 server with a remote Serena-Supplied Runtime RDBMS (see "Preparing a Remote Windows Serena-Supplied Runtime RDBMS" on page 86), the Oracle tables PCMS_DATA, PCMS_IDX, PCMS_TEMP, and PCMS_RBS are no longer installed during the installation of a Dimensions CM 14.1 server with either a local or remote Oracle database.
CMS-XML KM-Dim8: Tuning Oracle for best performance with Dimensions
DISK3 - PCMS_DATA tablespace files DISK4 - PCMS_RBS tablespace files DISK5 - PCMS_TEMP tablespace files
HTML How to Migrate Dimensions from one UNIX server to another
Before installing Oracle binaries and creating database files on the new target server, run the $PCMS_DBASE/oracle_sizing.sql script to determine the sizes of the tablespaces PCMS_DATA, PCMS_TEMP and PCMS_RBS . There may also be other tablespaces used for the storage of indexes (e.g. PCMS_INDEX), and these additional tablespaces will need to be recreated in the new instance prior to importing the database.
CMS-XML KM-Dim7: Error: ORACLE - Failed to allocate extent of in tablespace
and PCMS_RBS should both have at least 50Mb free space. It doesn't matter so much for PCMS_TEMP. PCMS_DATA should have as
CMS-XML 10.1.x / Oracle 10g : why requiring to set UNDO_MANAGEMENT to MANUAL ?
The undo_management set to manual serves only for backward compatibility. The database will work better with the undo_management set to auto and an undo tablespace size of about 1/4 of the PCMS_DATA tablespace size. Using the automatic undo_management will not affect the migration but one suggestion is to also keep the tablespace PCMS_RBS during the migration and it can be dropped once it is completed.
MS-WORD How to move an installation from one server to another
connect sys/change_on_install create tablespace pcms_rbs datafile 'd:\Win32App\PVCS\Dimensions\ORANT\Database\pcms_rbs_PCMS.dbf' size 20M
CMS-XML KM-Dim7: Check Shared_Pool_Size information, and the amount of freespace in the SYSTEM and ROLLBACK SEGMENTS.
FROM dba_free_space WHERE tablespace_name = ' PCMS_RBS '; sql> spool off
CMS-XML KM-Dim7: Error: ORA-01562, 00000, "failed to extend rollback segment (id = %s)"
SQLDBA> CREATE ROLLBACK SEGMENT <id> TABLESPACE PCMS_RBS STORAGE (INITIAL 200K
HTML Host Requirements for Dimensions Windows Clients
SYSTEM tablespace: 80 Mb PCMS_RBS tablespace for rollback segments: 20 Mb PCMS_TEMP tablespace: 10 Mb
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs