Database Error Messages

The iSQL*Plus Server could not completely execute the script because there was not enough memory available. Part of the script may have executed. Some specific causes are:

1. The Java VM heap grew too large due to executing scripts with large output or with too many concurrent sessions.
2. Insufficient physical memory available for the Java VM.

One or more of the following may help:

1. Edit queries to reduce the number of rows returned.
2. Turn iSQL*Plus multi page output on to reduce the number of rows cached.
3. Schedule large scripts sequentially.
4. Use Oracle Resource Manager to limit user queries.
5. Modify the iSQL*Plus OC4J startup script. Increase the -Xmx and -Xms values to allocate more memory to iSQL*Plus.
6. Review DDL and DCL that may have been executed prior to the memory shortage. Reexecute the script.

The iSQL*Plus Server could not completely execute the script because there was not enough memory available. Part of the script may have executed. Some specific causes are:

1. The Java VM heap grew too large due to executing scripts with large output or with too many concurrent sessions.
2. Insufficient physical memory available for the Java VM.

One or more of the following may help:

1. Edit queries to reduce the number of rows returned.
2. Turn iSQL*Plus multi page output on to reduce the number of rows cached.
3. Schedule large scripts sequentially.
4. Use Oracle Resource Manager to limit user queries.
5. Modify the iSQL*Plus OC4J startup script. Increase the -Xmx and -Xms values to allocate more memory to iSQL*Plus.
6. Review DDL and DCL that may have been executed prior to the memory shortage. Reexecute the script.

The iSQL*Plus Server could not completely execute the script because there was not enough memory available. Part of the script may have executed. Some specific causes are:

1. The Java VM heap grew too large due to executing scripts with large output or with too many concurrent sessions.
2. Insufficient physical memory available for the Java VM.

One or more of the following may help:

1. Edit queries to reduce the number of rows returned.
2. Turn iSQL*Plus multi page output on to reduce the number of rows cached.
3. Schedule large scripts sequentially.
4. Use Oracle Resource Manager to limit user queries.
5. Modify the iSQL*Plus OC4J startup script. Increase the -Xmx and -Xms values to allocate more memory to iSQL*Plus.
6. Review DDL and DCL that may have been executed prior to the memory shortage. Reexecute the script.