Friday, December 16, 2016

ORA-01113: file 1 needs media recovery ORA-01589: Must use RESETLOGS or NORESETLOGS option for database open

 
 ORA-01113: file 1 needs media recovery 
 ORA-01110: data file 1: 'C:\APP\RESWANTHREDDY\ORADATA\ORCL\SYSTEM01.DBF'

ORA-01589: Must use RESETLOGS or NORESETLOGS option for database open


SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open


SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'C:\APP\RESWANTHREDDY\ORADATA\ORCL\SYSTEM01.DBF'



=>Find the redo log file which belongs to current using below query.



SQL> SELECT MEMBER FROM V$LOG G, V$LOGFILE F WHERE G.GROUP# = F.GROUP# AND G.STA
TUS = 'CURRENT';


MEMBER
--------------------------------------------------------------------------------

C:\APP\RESWANTHREDDY\ORADATA\ORCL\REDO03.LOG



RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL



SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
ORA-00279: change 10897833 generated at 12/02/2016 20:55:41 needed for thread 1
ORA-00289: suggestion :
C:\APP\RESWANTHREDDY\FAST_RECOVERY_AREA\ORCL\ARCHIVELOG\2016_12_16\O1_MF_1_723_%

U_.ARC
ORA-00280: change 10897833 for thread 1 is in sequence #723


Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\APP\RESWANTHREDDY\ORADATA\ORCL\REDO03.LOG
Log applied.
Media recovery complete.






=> Open the database in RESETLOGS mode.
 
SQL> alter database open resetlogs;

Database altered.

SQL>

Thursday, December 1, 2016

Purging OBIEE Cache from OBIEE Report and Scheduling using BI Agent.

Purging OBIEE Cache from OBIEE Report and Scheduling using BI Agent.

1) Create New Connection Pool with ODBC 2.0 Type and Weblogic Server Username and Password.

2) Create New OBIEE Report from Create Direct Database Request.












3)  Connect Pool Name and Call SAPurgeAllCache(); command.




























4)  Run The Report and Schedule this report using BI Agent After Completion of ETL Loads and Add Mail Alert Notification.


Using Linux Shell Script to check OBIEE Server status and Sending Mail Alert


#!/bin/bash
#
#
#=============================================================================
# SCRIPT NAME        : check_bisever_status.sh
# SCRIPT DESCRIPTION : This script can be used for to verify bi server  status
# CREATE DATE        : Mar 12, 2016
# AUTHOR             : Raveendra Reddy T.
#=============================================================================
# call OBIEE Environemnt variables profile
#. .profile
cd /home/obiee

export today=$date
# Email Id
tomail=ravindratal@gmail.com
echo $todate
# Logfile 
export logfile=./biserver.log
# Using PS we will get the Process ID for bi_server1 server to check the status.
ps -ef |grep bi_server1 | grep -v grep <biserver.log

PID=`ps -eaf | grep bi_server1 | grep -v grep | awk '{print $2}'`

echo $PID <biserver.log
# Validating and sending mail server status. 
if [[ "" !=  "$PID" ]]; then
 mail -s "BI Server is UP & Running Fine  PID=> $PID " "Hi All, BI Server Is UP & Running Fine "    $tomail <biserver.log
else
mail -s "BI Server is not running " $tomail  <biserver.log
fi

echo $biserver
echo  "done"
exit

Wednesday, April 13, 2016

OBIEE 11.1.1.7 - Export to Excel 2007+ Error Shell format error

OBIEE 11.1.1.7 - Export to Excel 2007+ Error Shell format error

To Resove excel 2007 export and header fixed issues please follow the below two steps.

1) Applying OBIEE bundled patch 11.1.1.7.140415
2) Enable below parameter as TRUE in xdo.cfg Configuration file.

"xlsx-keep-values-in-same-column" set to true  in xdo.cfg configuration file.
 
It will be available in below instance config BIJava Host components directory.


/obiee/Middleware/instances/instance1/config/OracleBIJavaHostComponent/coreapplication_obijh1/
xdo.cfg 


<config version="1.0.0" xmlns="http://xmlns.oracle.com/oxp/config/">
<properties>
<property name="xlsx-keep-values-in-same-column">true</property>
</properties>
</config>


ODI XML File Parallel exeuction errors.

PARALLEL EXECUTION OF XML DRIVER COMMANDS FAIL


If you are running XML Files files parallel you will get xml error on technology

Use below two parameters in JDBC URL:  &dod=true&re=true

OR

update below patch no


 Patch 18238917: PARALLEL EXECUTION OF XML DRIVER COMMANDS FAIL

Configuring ODI Master and Work repositories in RAC Database using JDBC URL Format.



Configuring ODI Master and Work repositories in RAC Database using below JDBC URL Format.


jdbc:oracle:thin:(DESCRIPTION = (LOAD_BALANCE=ON) (ADDRESS = (PROTOCOL = tcp)
(HOST = 192.168.1.10)(PORT = 1521)) (ADDRESS = (PROTOCOL = tcp)(HOST = 192.168.1.11)
(PORT = 1522)) (CONNECT_DATA = (SERVER=dedicated)

(SERVICE_NAME=PROD_EDW)))

Sunday, November 15, 2015

ERROR: ORA-12154: TNS:could not resolve the connect identifier specified

ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified

Note:  Before doing this activity Pls take a backup of init.ora.5132015144713 and listener.ora files.


C:\Users\Sindhu>lsnrctl start

LSNRCTL for 64-bit Windows: Version 12.1.0.1.0 - Production on 15-NOV-2015 14:01
:13

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Starting tnslsnr: please wait...

TNSLSNR for 64-bit Windows: Version 12.1.0.1.0 - Production
System parameter file is E:\app\Sindhu\product\12.1.0\dbhome_1\network\admin\lis
tener.ora
Log messages written to E:\app\Sindhu\diag\tnslsnr\lucky\listener\alert\log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521
ipc)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 12.1.0.1.0 - Produ
ction
Start Date                15-NOV-2015 14:01:18
Uptime                    0 days 0 hr. 0 min. 8 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Default Service           CLRExtProc
Listener Parameter File   E:\app\Sindhu\product\12.1.0\dbhome_1\network\admin\li
stener.ora
Listener Log File         E:\app\Sindhu\diag\tnslsnr\lucky\listener\alert\log.xm
l
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
  Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully


Solution:

SQL> alter system set LOCAL_LISTENER='(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PO
RT=1521))' scope=both;

System altered.

SQL> alter system register;

System altered.


OR

Comment #local_listener=LISTENER_ORCL line in  init.ora.5132015144713 file.



SQL> startup pfile=C:\app\Sindhu\admin\orcl\pfile\init.ora.5132015144713;
ORACLE instance started.

Total System Global Area 2438529024 bytes
Fixed Size                  2405568 bytes
Variable Size             654314304 bytes
Database Buffers         1761607680 bytes
Redo Buffers               20201472 bytes
Database mounted.
Database opened.

SQL> create spfile from pfile='C:\app\Sindhu\admin\orcl\pfile\init.ora.513201514
4713';

File created.








Connected to an idle instance. ORA-00132: syntax error or unresolved network name 'LISTENER_ORCL'

SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_ORCL'



SQL> create pfile from spfile;

File created.

SQL> create spfile from pfile;

File created.

SQL> startup
ORACLE instance started.

Total System Global Area 6396977152 bytes
Fixed Size                  2416968 bytes
Variable Size            1207963320 bytes
Database Buffers         5167382528 bytes
Redo Buffers               19214336 bytes
Database mounted.
Database opened.
SQL> conn sys as sysdba
Enter password:
Connected.

SQL>