OSM Order Fails With ORA-01658: Unable To Create INITIAL Extent For Segment In Tablespace
(Doc ID 2071992.1)
Last updated on MARCH 16, 2023
Applies to:Oracle Communications Order and Service Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
OSM 184.108.40.206.2 - fresh install
Oracle Database 220.127.116.11 . Database is configured as single instance on RAC cluster
When placing sample orders available under O2A PIP (OracleComms_OSM_O2A_COM_CSO_SalesOrders cartridge) error ORA-01658 appears. The tablespace created for Order Data is getting full very quickly and throwing below error :
TS_LARGE_DATA TS tablespace was created with 2GB initial space with max limit of 4GB using the syntax below:
CREATE SMALLFILE TABLESPACE TS_LARGE_DATA LOGGING DATAFILE SIZE 2G AUTOEXTEND ON NEXT 10M maxsize 4g;
After the first test order tablespace size is full and it is auto extended and for another order it is again auto extended and by this time TS size is 4GB.
At this stage when trying to fire another order ORA-01658 appeared and it makes sense but the issue is why 4GB tablespace is used for just couple of test orders?
Note: The osm parameter 'oracle.communications.ordermanagement.order.CompressXMLValues' value is true and the database parameter 'deferred_segment_creation' is also true. All other 3 Tablespaces are normal in utilization, only TS_LARGE_DATA is consumed very quickly.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document