[chrisplough]

Naveen,

This error occurs because your INDX tablespace is too small. Add 2GB to this tablespace and restart the DB import process. Ensure that you start from running the create_glog_roles.sql and create_glog_users.sql scripts in order to delete the existing data.

--Chris

[nick.polites]

This is indicating that your INDX tablespace is full and can't be extended. Do you have autoextend on for this tablespace? If you do then you are out of physical disk space.

[svenhaul]

I have a further comment to the original problem, the JVM not starting. I had the same problem on a Win32 box, but the ms and mx parameters where set correctly to 1024m, and enough physical memory available.

It turned out that the JVM throws that error even on a one-line "Hello world" java class started from the command line if started with -XX:MaxPermSize=384m and the other parameters.

Sun's comment on the -XX parameters does not give much, apart from that they might change anytime.

It seems that Win32 has a size limitation on the memory one DLL can allocate. All the specified memory requests together might not be fulfilled, regardless of the installed and apparently free memory.

To get things going, I changed the following lines from %otm%\oas\bin\oc4j.conf:

wrapper.java.additional.2=-Xms512m
wrapper.java.additional.3=-Xmx820m
wrapper.java.additional.8=-XX:MaxPermSize=384m
wrapper.java.additional.9=-XX:NewSize=256m
wrapper.java.additional.10=-XX:MaxNewSize=256m

After that, the service does start.

I know that these tuning parameters are there for a reason, but I am currently setting up a pure test and evaluation box, so the last few percent of performance are not the primary interest. For a production environment, one would certainly want to dig further into the issue.

These values might very well depend on the specific circumstances - I basically tried them out. As far as I understood the JVM docs, MaxPermSize is the most important, as it does govern how many classes can be loaded.

[chrisplough]

Just FYI, the following 2 parameters are strictly for performance and you'll likely want to evaluate for PROD:

#wrapper.java.additional.9=-XX:NewSize=256m
#wrapper.java.additional.10=-XX:MaxNewSize=256m

However, the following parameter is usually required for the OTM web and app server to startup correctly - as this defines the memory space that the JVM uses to hold objects like classes and methods. (Reference: -XX:MaxPermSize - CauchoWiki ) If this is undersized, sometimes OTM won't start -- and other times it will simply crash when large workloads are processed.

#wrapper.java.additional.8=-XX:MaxPermSize=384m

The problem with running on Win32 is that your total JVM memory size (MaxPermSize + heap) is limited to somewhere between 1200 and 1400MB, depending on how fragmented your memory is at the time the JVM starts up. As a result, you may have difficulties running any significant volumes on Win32 in PROD, as most OTM installations require a heap size of 1536MB to 2304MB for optimal performance.

Hope this helps.

--Chris