-
Title
Internal error: 10720 - can't add queue writer que_BADUSER: Illegal user name specified -
Description
Capture generates "Internal error: 10720 - can't add queue writer que_BADUSER: Illegal user name specified" and exits, after activation.
-
Resolution
This is caused by entry in sqlnet.ora not set to the default domain, so in order for the user to run ora_setup, the sidname with the connect string has to be used. This will create a long datasource string with periods as delimiters in the config file, such as "datasource:o.<SID>.<NAME>.<COMPANY>.<COM> ", instead of "datasource:o.<SID>".
Other related errors:
Error: 17000 - Error opening file <$SP_SYS_VARDIR>/state/o.<SID>.<NAME>.<COMPANY>.<COMN>-objcache.<ACTID>: No such file or directory.
RESOLUTION
1. Check if the $SP_SYS_VARDIR/config/config file contains a long datasource strings with delimiters, such as "datasource:o.<SID>.<NAME>.<COMPANY>.<COM> ".
2. Check if the $SP_SYS_VARDIR/data/paramdb file's SP_ORD_OWNER contain a long sid name with delimiters, such as "SP_ORD_OWNER_O.<SID>.<NAME>.<COMPANY>.<COM> "splex""
3. Check the etc/hosts file and make sure the IP to hostname to alias resolves on source and target
4. Go to the $ORACLE_HOME/network/admin/
5. Edit the sqlnet.ora file and see if the "NAMES.DEFAULT_DOMAIN" parameter is set.
For example: "NAMES.DEFAULT_DOMAIN = <name>.<company>.<com>"
6. If the "NAMES.DEFAULT_DOMAIN" parameter exists on the sqlnet.ora file, verify if using Oracle Names. If using Oracle Names, the sqlnet.ora file will also contain the following:
NAMES.DIRECTORY_PATH = (TNSNAMES,ONAMES)
NAMES.DEFAULT_DOMAIN
NAMES.DEFAULT_ZONE
NAMES.PREFERRED_SERVERS
NAME.PREFERRED_SERVERS
7. If not using Oracle Names, comment the "NAMES.DEFAULT_DOMAIN = <name>.<company>.<com>" from the sqlnet.ora. Otherwise reference your SharePlex installation Guide or call Support.
8. Save the changes made to the sqlnet.ora and exit the edit
9. Make sure that the sid_name or service_name string is correct in the listener.ora file to have the correct global name. Use the hostname in the listener.ora instead of the IP address in /etc/ hosts file.
10. View the init<SID>.ora and note the values for db_name, instance_name, and service_names.
11. If the listener.ora file contains "(GLOBAL_DBNAME = <SID>.<name>.<company>.<com>", comment and add (GLOBAL_DBNAME = <SID>) instead.
12. Save the changes made to the listener.ora file and exit the editor
13. Bounce the listener
14. Shutdown SharePlex
15. Make sure that an entry exists in the oratab file for this SID and ORACLE_HOME.
16. Run ora_cleansp on both source and target
17. Re-run ora_setup using the Oracle sid name without the @ connect string
18. Edit the config file to have only the SID_NAME as the "o.sid" string and remove the long datasource name (Datasource:o.<SID>.<NAME>.<COMPANY>.<COM>) from the config file,
19. Save the changes made to the config file and exit the editor,
20. Activate config.