Recoving Oracle..'Wind' database...

It may happen that we might have an Oracle database crash power  down situations and Oracle never comes up.  Oracle might never come up due to corrupt block or any other issues. There may be errors like ORA-01578 or corruption.

There are some simple steps we need to follow

SQL>sqlplus / as sysdba

SQL> shutdown immediate

SQL> startup nomount

SQL>alter database open;

If all these steps go through without any issues then you the lucky person and there are no issues.

In case there is a real corruption we may have to recover the database In this Situation we need to recover the database using REDO logs.

Follow below steps

Take a backup of the entire OCU folder

SQL>sqlplus / as sysdba

SQL> shutdown immediate

SQL> startup nomount

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

This query outputs the path of the redo log that we need to submit in the next query.

SQL>recover database until cancel

In this step you should the path the is obtained in the above step

SQL>alter database open resetlogs;

If none of the above work then we need to create a new set of control files in addition to the above steps,

Follow below steps

Take a backup of the entire OCU folder and delete the .CTL files from the OCU folder.

SQL>sqlplus / as sysdba

SQL> shutdown immediate

SQL> startup nomount

SQL>CREATE CONTROLFILE REUSE DATABASE "WIND" RESETLOGS NOARCHIVELOG

    MAXLOGFILES 16

    MAXLOGMEMBERS 3

    MAXDATAFILES 100

    MAXINSTANCES 8

    MAXLOGHISTORY 292

LOGFILE

  GROUP 1 'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDREDO01.LOG'  SIZE 100M,

  GROUP 2 'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDREDO02.LOG'  SIZE 100M,

  GROUP 3 'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDREDO03.LOG'  SIZE 100M

DATAFILE

  'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDBLOBS01.DBF',

  'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDINDEX01.DBF',

  'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDSYSAUX01.DBF',

  'D:\ptc\Windchill_9.1\ocu\oraata\wind\WINDSYSTEM01.DBF',

  'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDUNDOTBS01.DBF',

  'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDUSERS01.DBF',

  'D:\ptc\Windchill_9.1\ocu\oradata\wind\WINDWCAUDIT01.DBF'

;

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

This query outputs the path of the redo log that we need to submit in the next query.

SQL>recover database until cancel

In this step you should the path the is obtained in the above step

SQL>alter database open resetlogs;

These all 3 methods usually suffice to recover a crashed database. But if even these 3 methods donot recover your database then you need to get in touch with a database expert.

JExplorer..LDAP jobs made easy

The new WindChillDS UI is too complex and boring to work on. I tried to search some tools which could be handy to work on LDAP and found this tool JExplorer.

This tool gives the feel of the old Aphelion browser and has many cool feature that makes it way handy than WindChillDS.

Where to get it…

http://jxplorer.org/downloads/users.html

it is pretty straight forward to use .

Its features;

http://jxplorer.org/features.html

Here is if you need more information,

http://jxplorer.org/documents/JXv3.2_Administrator_Guide.pdf

Tell me…what you want to see

I am always thinking of new topic to put up here to help many others who are into Windchill….please reply to this topic below if you want to see any specific topic here that you think might not only help you but several other PLM engineers as well. I will try my best to write an article on it.

Regards,

Rohan

Fiddler to debug Windchill issues on Internet Explorer

Fiddler can be helpful for:

1. Find files/java scripts that are accessed by the client from the server.

2. When we encounter a strange performance work bottleneck in IE that you can't track down.

3. Task is not executable only on Internet Explorer

4. Able to perform a Specific web activity only on Firefox and not on IE

Fiddler works only with IE

What does Fiddler Fiddle with:

Fiddler records all HTTP(S) traffic, set breakpoints, and "fiddle" with incoming or outgoing data.

System Requirements

Windows 2000 / XP / 2003 / Vista with Microsoft .NET Framework v2.0 +
10 megabytes disk space / 800mhz processor (Screams at 2.4ghz)
128 megabytes RAM (512mb+ highly recommended)

Link to Download Fiddler

http://www.fiddler2.com/fiddler2/version.asp

A Picture speaks 1000 words: Fiddler Layout

HTTP Statistics view

By exposing all HTTP traffic, Fiddler easily shows which files are used to generate a given page. Using the Statistics page, the user can multiselect to get a "total page weight"—the number of requests and the bytes transferred

Additionally, by exposing HTTP Headers in the Session list, the user can see whether pages are missing HTTP Expiration headers that permit client or proxy caching. If a response does not contain Expires or Cache-Control headers, it might not be cached by the client.

Using Fiddler for Debugging

In addition to seeing all HTTP requests and responses, Fiddler supports the notion of breakpoints. When the Enable Single Step Debugging option is checked on the Rules menu, or when the properties of the HTTP Request or Response match the target criteria, Fiddler can pause HTTP traffic and allow edits. This feature proves useful for security testing, as well as for general functionality testing, because all code paths can be exercised.