Hi, we've imported an Oracle 18.104.22.168 db into Oracle10.2.0.3.0 and want to change the init params according to the 22.214.171.124. production db.
ALTER SYSTEM SET processes=10000 SCOPE=SPFILE;
We can't start the 10g DB: ORA-00064: object is too large to allocate on this O/S (1,5150880)
When reducing the size to 500 there is no problem starting the db.
Question: The node has the same configuration as the one on which the 126.96.36.199 is installed. The 188.8.131.52. does actually run with processes=10000. Can you give me a hint where to search? Should we alter extra parameter(s)?
1) did you check the (solaris) OS kernel parameters - are they the same on your two servers?
- Check Metalink for how to set these values for larger numbers of users/processes
(sorry, I have no access at the moment)
2) do you really need 10.000 processes (ten thousand it says in your detail, only 1000 in the post title). That's a lot of sessions!! How many sessions are you really expecting? You can try increasing the parameter
500, 1.000, 2.000, 5.000, 10.000 and see what happens.
I have exactly the same problem. I've changed PROCESS parameter to 3000 and Oracle does not start anymore.
My database is on Windows Server 2003 and Oracle 10.2.0
How can I change the parameter back to the previous value if Oracle is not started? I've tried thru ALTER SYSTEM command but got a ora01034...
I'm no DBA and have no clue on how to do this.
If there is no such parameter in initSID.ora, then you are using spfile. Do the following:
sqlplus "/as sysdba"
create pfile from spfile; -- without starting the instance
edit the pfile to change the processes parameter, delete spfile
create spfile from pfile
This error shows that your session with oracle database has been ended.
If database is still running then you can simply reconnect and continue.
ORA-3113 could be signaled for any of these scenarios:
- Server machine crashed
- Your server process was killed at O/S level
- Network problems
- Oracle internal errors / aborts on the server
- Client incorrectly handling multiple connections
- etc.. etc.. etc.. - a lot of possible causes !!
check if your database is running or not on unix enter this command
ps -ef|grep smon
if it show you smon_YOURDBSID then you db is running.