Replication job failures due to resource limits 
Author Message
 Replication job failures due to resource limits

We are running a multi-master replication environment on Oracle 8051 and
 SUN solaris 2.6. I have attempted to enforce user profile resource
limits by setting the init.ora parameter RESOURCE_LIMIT = true. As soon
as this is done, all replication jobs fail with:

ORA-02394: exceeded session limit on IO usage, you are being logged off

All replication jobs are owned and executed by the replication admin
user. The profile to which the replication admin user belongs to has all
resources set to "UNLIMITED". I've tried setting the profile
reads/session to 999999999. This doesn't make any difference.

All ideas would be greatly appreciated.

Colin.

Sent via Deja.com http://www.***.com/
Before you buy.



Wed, 18 Jun 1902 08:00:00 GMT
 Replication job failures due to resource limits

Did you check the resource limit settings in both databases?

dave


Quote:

> We are running a multi-master replication environment on Oracle 8051
and
>  SUN solaris 2.6. I have attempted to enforce user profile resource
> limits by setting the init.ora parameter RESOURCE_LIMIT = true. As
soon
> as this is done, all replication jobs fail with:

> ORA-02394: exceeded session limit on IO usage, you are being logged
off

> All replication jobs are owned and executed by the replication admin
> user. The profile to which the replication admin user belongs to has
all
> resources set to "UNLIMITED". I've tried setting the profile
> reads/session to 999999999. This doesn't make any difference.

> All ideas would be greatly appreciated.

> Colin.

> Sent via Deja.com http://www.deja.com/
> Before you buy.

Sent via Deja.com http://www.deja.com/
Before you buy.


Wed, 18 Jun 1902 08:00:00 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. job is stuck due to connection failure

2. SQL 6.5 replication failure due to not enough locks

3. Unauthorized due to ACL on resource

4. SQL Server will not start, due to Log in failure

5. Login failure due to licensing (MSDN?)

6. MSSQLServer service fails to start due to logon failure

7. Error 1069 - Service did not start due to a logon failure

8. error 1069 - (The service did not start due to logon failure)

9. Failures due to open connections

10. Merge Failures due to deadlocks

11. Failed initial synchronization due to failure to open subscribing database

12. Connection failure due to insufficient memory


 
Powered by phpBB® Forum Software