Redis user permissions (ACL) and python connection

-
 Recently, I was working on setting up a redis cluster along with separate users for readwrite and readonly. I setup the readonly user using the below privileges (ACLs):   user redisreadonly on >mySuperSecretPassword ~* resetchannels -@all +@read +ping +asking   Once this is setup, I wrote a simple program in python to connect to the redis cluster using the readonly credentials and print the number of keys.   #!/usr/bin/env python3 """ pip3 install redis """ from redis.cluster import RedisCluster, ClusterNode # ─────── Cluster connection ─────── startup_nodes = [ ClusterNode("redis_host_1", 6379), ClusterNode("redis_host_2", 6379), ClusterNode("redis_host_3", 6379) ] rc = RedisCluster(startup_nodes=startup_nodes,decode_responses=True,username='redisreadonly',password='mySuperSecretPassw...
Post a Comment

ORA-07445 [kopxccc()+124] error trying to submit a concurrent request

-
I am writing this blog entry to share an interesting error with you. There is a parameter ORA_NLS10 without setting which, the database was throwing a lot of ORA-07445 errors. I spoke about the ORA_NLS10 parameter in a previous post. A related issue was occuring here too.

Issue

Unable to submit concurrent requests. Receiving the below error:

APP-FND-01564: ORACLE error 3113 in FDFDDS_RAISE_DFF_COMPILED


Also, receiving ORA-07445 errors in the alert log.

Mon May 17 05:54:00 2010
Completed: ALTER DATABASE OPEN
Mon May 17 05:57:12 2010
Errors in file /u005/app/oracle/cpe2eprd/cpe2eprddb/10.2.0/admin/cpe2eprd_cpeidb/udump/cpe2eprd_ora_1094.trc:
ORA-07445: exception encountered: core dump [lfilic()+328] [SIGSEGV] [Address not mapped to object] [0x000000040] [] []
Mon May 17 06:03:18 2010
Errors in file /u005/app/oracle/cpe2eprd/cpe2eprddb/10.2.0/admin/cpe2eprd_cpeidb/udump/cpe2eprd_ora_2966.trc:
ORA-07445: exception encountered: core dump [kopxccc()+124] [SIGSEGV] [Address not mapped to object] [0x000000062] [] []
Mon May 17 06:06:40 2010
Errors in file /u005/app/oracle/cpe2eprd/cpe2eprddb/10.2.0/admin/cpe2eprd_cpeidb/udump/cpe2eprd_ora_3956.trc:
ORA-07445: exception encountered: core dump [kopxccc()+124] [SIGSEGV] [Address not mapped to object] [0x000000062] [] []


Cause

Database was started with incorrect ORA_NLS10 parameter.

Analysis

As per MOS Note ID: 553264.1, ORA_NLS10 parameter should be set to $ORACLE_HOME/nls/data/9idata.

Solution

1. Shutdown the database.

2. Set the parameter ORA_NLS10 to the correct value as per MOS Note ID: 553264.1

export ORA_NLS10=$ORACLE_HOME/nls/data/9idata

3. Startup the database.


References

1. MOS Note ID: 553264.1

Comments

Post a Comment

Popular posts from this blog

Interesting Oracle Applications (EBS) Interview Questions

-
Below are some interesting interview questions that I have faced over the years. What is the difference between a concurrent manager and a cron job? Can one patch a CRS Oracle home with the CRS services up? Suppose, there are 2 nodes node1 and node2 with CRS cluster and one wants to patch node1. Can it be done with node2 being up? Suppose one fires a select statement and the data does not in the library cache, then the data, obviously, has to be fetched from the data files. Which background process is used for this purpose? What are the sizing requirements for say, a 100 concurrent users Oracle Apps Installation? What is the difference between a shared appl_top and a staged appl_top?
Read more

Modify retention period of workflow queues

-
Yesterday, there was a requirement to increase the retention period of WF_DEFERRED and WF_BPEL_Q so that the developers could troubleshoot issues involving business events. This can be done this way: 1. Check the retention period of existing workqueues. SQL> SELECT owner, name, retention FROM all_queues WHERE name LIKE 'WF%'; OWNER           NAME                                                RETENTION --------------- --------------------------------------------- ------------------------------ APPS                 WF_BPEL_Q                                                0 APPLSYS         WF_INBOUND_QUEUE              ...
Read more

Check if UTL_FILE and FND_FILE are working fine

-
Yesterday, while troubleshooting a vexing ORA-29280 error, I came across 2 useful PL/SQL anonymous blocks that can be used to test FND_FILE and UTL_FILE to find out whether they are indeed working fine. UTL_FILE set serveroutput on DECLARE file_location VARCHAR2(256) := '<first entry on utl_file_dir>'; file_name VARCHAR2(256) := 'utlfile1.lst'; file_text VARCHAR2(256) := 'THIS IS A TEST'; file_id UTL_FILE.file_type; BEGIN file_id := UTL_FILE.fopen(file_Location, file_name, 'W'); UTL_FILE.put_line(file_id, file_text); UTL_FILE.fclose(file_id); EXCEPTION WHEN UTL_FILE.INVALID_PATH THEN dbms_output.put_line('Invalid path ' || SQLERRM); WHEN OTHERS THEN dbms_output.put_line('Others '|| SQLCODE || ' ' || SQLERRM); END; / References: Metalink (MOS) Note ID: 261693.1 FND_FILE set serveroutput on exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'THIS IS A TEST'); HTH....
Read more