Hi, We're having a shared memory issue while using 'Migrate storage' tool. We recently migrated from SDE 9.3 to 10.2.1 and Oracle 10g to 11gR2. Everything else work fine but we get this error only when we use 'Migrate Storage' tool. We're trying to migrate 9.3 ESRI Binary spatial type to ST_Geometry.
ORA-12853: insufficient memory for PX buffers: current 229936K, max needed 16879104K ORA-0431:unable to allocate 65560 bytes of shared memory (�??large pool�?�, unknown object�?�, �??large pool�?�, �??PX msg pool�?�)
Have anyone experienced this? Thank for your help in advance.
It sounds like your database needs more resources allocated to the SGA in order to perform the operation. You can reconfigure your Oracle database's SGA to include at least (max - current) bytes of additional memory. Try making the MAX SIZE and TARGET values the same: create pfile from spfile (must be done as sys user) ALTER SYSTEM SET sga_max_size=16879104K scope=spfile; ALTER SYSTEM SET sga_target=16879104K scope=spfile; SHUTDOWN IMMEDIATE STARTUP show parameter sga_max_size show parameter sga_target
If the database starts up without issue, then: create pfile from spfile
If it does not come start up, then perform these steps: SHUTDOWN IMMEDIATE startup pfile=<path to pfile> Alter SGA to whatever values were configured from your old settings (229936K) with scope=spfile SHUTDOWN IMMEDIATE STARTUP (which should start from spfile)
If the database starts correctly, then: create pfile from spfile
Not everyone has the RAM necessary to allocate 16+Gb to the SGA. If you have some seriously massive geometries that exceed the ability to migrate in situ, you may need to export the troublesome table(s), truncate them, then migrate the empty template and append the export file contents.
This of course assumes the table is a simple feature class (not versioned, not using geodatabase behaviors,...). If it isn't simple, migration should still be possible, but it will be more involved.
Vince, You are right, I don't think we can allocate 16GB of RAM.
We get this error everytime we use this tool for almost all the feature classes regardless of it's size. We have been doing a work around as you mentioned, copying and pasting the data to migrate the storage type but it is not feasible for the datasets that are versioned and have archiving enabled. Do you know if it's is a bug with Migrate Storage tool? Why is it consuming so much memory resources? Thanks in advance.