How to check and see if Oracle Account is expired, locked, or open

In the EPM world, things are tricky sometimes because of too many things inter-related for the EPM system to work as a whole.

It comprises of several things
     The EPM System itself which is made up of several things - the most common, for example, being, Shared Services, Foundation, Essbase, Planning, plus the reporting and analysis tools - the financial reporting studio and web analysis. Then we have the Print services which seems very trivial but of equal importance and the Ghostscript (at least in the 11.1.2. version).
     Then, we have Smartview or Excel add-in and Web Logic
      Last but not the least, one of the most important piece of software - the database. We have the 11G in this case.

While working in the EPM environment, a slight issue in any of the above-mentioned area can lead up to errors, and because of the magnanimity of the EPM structure, the numbers of log files it creates, and the hard-to-remember path, it is sometimes a pain-in the-neck to resolve the issue.

Let me share this. Our secondary system was working fine and suddenly, one fine morning, while trying to pull up a financial report in workspace, it threw out an error. After having checked all the logs, checking the documentation, and doing some GOOGLE, we came to find out that the BIPLUS account password had expired. We never knew that those passwords would expire. It took so long to find out the cause of the error, however, after getting the information regarding the password expiry, all we had to do was set the password again and we were ready to rock.

In such cases, it is handy to check and see if any of the Oracle user accounts have expired. This is how you do it.
Open SQLPLUS.
Enter admin Username and ENTER
Enter password and ENTER
Now on the SQL> prompt, you can type in the command:
           SELECT username, account_status
           FROM dba_users;
It will give you a list of USERNAMEs and ACCOUNT_STATUS
ACCOUNT_STATUS will be OPEN, EXPIRED, or EXPIRED & LOCKED

How to change Essbase INDEX and PAGING file location

When we create Essbase cube, the INDEX (.ind) and PAGING (.pag) files are by default created under the app-database directory. For example, if you have Essbase installed in “D” drive, and if I have an application.database named Khoonks.Nirmal, the INDEX and PAGING files would be located under \\servername\d$\HYPERION\ESSBASE\app\Khoonks\Nirmal.

The names of the files would be NIRMAL.IND and NIRMAL.PAG.

It is not a problem in the initial stages, however, as the database size keeps on increasing, it takes longer during database restructure, outline changes, calculations, etc. Therefore, it is a good idea to change the location of the INDEX and PAGING files.

This is how you can change the storage location. 

In this example, we are changing the location from “D” to “E” drive.

1             Export the database.

2             Clear ALL DATA.

3             Modify the database location.  

a.       Right-click the database -> Edit -> Properties. You will see DATABASE PROPERTIES dialog.

b.      Click on STORAGE tab.

c.       Under “DISK VOLUME” you will see text “Click here to add.” Click it.

d.      From the DROP-DOWN, choose E.

e.      Click “SET.” “APPLY” “CLOSE”

4            Restart the application.

5            Load data from the export you did in step 1.

6           Check the new STORAGE location by Right-clicking the database -> Edit -> Properties. You can see the     new file location – path like \\servername\e$\Hyperion\Essbase\APP\Khoonks\Nirmal

7            Agg the database.