Wednesday, March 27, 2019

ORA-00600: internal error code, arguments: [kkdlron-max-objid], [4254950911], [4254950914]

When the database reached maximum object id or if the new object id exceeds the limit you will see below error. This situation normally happen in Data ware house databases, especially with SAP BW using Oracle as database.

< ORA-00600: internal error code, arguments: [kkdlron-max-objid], [4254950911], [4254950914], [], [], [], [], [], [], [], [], [] < ORA-00600: internal error code, arguments: [kewrose_1], [600]

You will get the max object id by running below commands.
SQL> select max(obj#) from SYS.obj$;
MAX(OBJ#)
----------
4254909633
SQL> SELECT dataobj# FROM sys.obj$ where name='_NEXT_OBJECT';
SQL> select max(object_id),max(DATA_OBJECT_ID) from dba_objects ;


Oracle Support Document 20529650.8 (Bug 20529650 - ORA-600 [kkdlron-max-objid], [4254950911]) can be found at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=20529650.8

Also check SAP note : 2137109 - Data Object ID limit , if you see the issue on SAP related applications.

I see 2 options here
1. Logically rebuild the DB - Permanent fix
2. Apply the patch 20529650 - workaround/temporary fix

The option 2 applying the patch will brings us the new limit 4293950911 (4254950911+39000000). But keep in mind that this new limit can reach quickly in BW systems. Note that the patch will give team some time but the permanent solution is to rebuilding the database.

You can use below query to estimate how much time you might have , but note that this is just an estimate only.


Regards
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com

Enable access to the Tableau Server repository (Postgres) and update repository access job has failed

Users can connect to tableau server repository suing tableau desktop using 2 built-in user’s i.e tableau, readonly. For reading database tableau and in-depth analysis it is recommended to use readonly user.

Before you use readonly user you need to enable the access . In older versions you will be using “tabadmin” command and in newer versions you will be using “tsm”.

Users will be connecting to tableau repository using port 8060.

Run below command to enable repository access

tabadmin dbpass --username readonly <password>

or

tsm data-access repository-access enable --repository-username readonly --repository-password <password >

When enabling the "readonly" user access i have received error using TSM.

61% - The services failed to stop. 66% - Disabling database services.
72% - Waiting for database services to disable.
The update repository access job has failed.
or
66% - An error occurred while waiting for services to reconfigure.
73% - Disabling database services.
80% - Waiting for database services to disable.
The update repository access job has failed. 

I tried different ways but didn’t help. Finally I have stopped the services and ran the above TSM command and it executed successfully.

Steps:
stop tableau services using TSM
run the command - tsm data-access repository-access enable --repository-username readonly --repository-password <password > 
start tableau services using TSM

This operation will perform a server restart. Are you sure you wish to continue?
(y/n): y
Starting update repository access asynchronous job.
Job id is '8', timeout is 25 minutes.
5% - Enabling the maintenance app.
11% - Waiting for the maintenance app to start.
16% - Reading configuration.
22% - Putting the repository into local trust mode.
27% - Enabling the database services.
33% - Waiting for the database services to enable.
38% - Updating the roles in the repository.
44% - Taking the repository out of local trust mode.
50% - Updated pending configuration.
55% - Disabling all services.
61% - Waiting for the services to stop.
66% - Updating the configuration version on nodes.
72% - Waiting for services to reconfigure.
77% - Enabling all services.
83% - Waiting for the services to start.
88% - Reloading postgres configuration.
94% - Disabling database services.
100% - Waiting for database services to disable.
Successfully updated repository access.

Regards
Satishbabu Gunukula, Oracle ACE

Error: Search & Browse is not available: Make sure all Tableau related files and windows are closed

Users may encounter below error when working with Tableau stop/start.

"***Error: Search & Browse is not available: Make sure all Tableau related files and windows are closed, then stop the server, run "tabadmin reindex" and start the services"

Unable to determine if all components of the service started properly. See tabadmin.log for more information.

When you see this error user unable to connect to tableau and check tabamin.log for more details.

After troubleshooting I ran cleanup with reset coordination and issue has been resolved.

Tabadmin stop
Tabadmin cleanup --reset-coordination
Tabadmin start

Thanks
Satishbabu Gunukula, Oracle ACE

Monday, February 18, 2019

Webinar: Data Guard Physical Standby Setup in Oracle?

This Webinar helps you to understand the benefits of Oracle Data Guard, available methods and how to setup and common issues.

Date and time: Feb 28th 2019 8:00am-9:00am
Pacific Daylight Time (San Francisco, GMT-07:00)

This Webinar covers following Topics.
· Oracle Data Guard and its Benefits
· Overview of different Data Guard Options
· Difference between RAC vs DG
· Prerequisites
· DataGuard Demonstration
· Common Issues
· Post verification Steps
· References
· Contact Info
· Q&A

To register for this Webinar, please send an email to SatishbabuGunukula@gmail.com.

Note that registrations are limited and first come and first serve basis.
You will receive an email confirmation with meeting session link.

For presentation link Click here

Regards,
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com

Tuesday, January 15, 2019

ORA-28040: No matching authentication protocol after Oracle 12c upgrade.

After Oracle 12c upgrade users started seeing below errors

ORA-28040: No matching authentication protocol

The main issue is older versions of drivers will not able to connect 12c server. In Oracle 12.1, the default value for the SQLNET.ALLOWED_LOGON_VERSION parameter is set to 11. This means that database clients using pre-11g drivers cannot authenticate to 12.1 database servers unless the SQLNET.ALLOWED_LOGON_VERSION parameter is set to the old default of 8 in $ORACLE_HOME/network/admin/sqlnet.ora

SQLNET.ALLOWED_LOGON_VERSION_CLIENT = 8
SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8

Note that SQLNET.ALLOWED_LOGON_VERSION has been deprecated in 12c.

Even after updating above values users might receive below error.
ORA-01017: invalid username/password: logon denied

In this case users need to add following parameter to sqlnet.ora
SQLNET.AUTHENTICATION_SERVICES = (NONE)

Also few users received ORA-28040 error when creating older version of databases (for ex: 10g) using DBCA

Thanks
Satishbabu Gunukula, Oracle ACE
https://oracleracexpert.com

Wednesday, January 2, 2019

Physical standby redo log must be renamed

When creating standby database using database duplication it completed but received below standby redo error. This error will not stop the replication but user don’t want to see these ORA- errors.

Finished recover at 2019-02-12:15:02:32
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/oracle/redo1/ORCL/ ORCL _1A.rdo'

RMAN-05535: warning: All redo log files were not defined properly.
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/oracle/redo1/ORCL/ORCL _2A.rdo'


Though this didn't stop the data guard replication, the customer wanted to get-rid the message. Starting with v10g, this was an expected behavior to improve the switchover and failover. With v10g, when MRP is started, it will attempt to clear the online log files.

If PRIMARY and STANDBY has the same directory structure then you will see these errors. This is an expected behavior when you don’t set log_file_name_convert parameter. You can get rid-off the error message just setup dummy value

SQL> ALTER SYSTEM SET log_file_name_convert='dummy','dummy';

You should not see ORA messages any more in the alert.log file.

Thanks
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com