Data Analyst Roles & Responsibilities: Environment :- MS SQL Server 2008 client & SERVER, MS office, Legacy - Mainframes, Titanium, Rational Clear Quest, Clear Case.
Professional Summary: 8 years of Industry experience as a Data Analyst with solid understanding of Data Modeling, Evaluating Data Sources and strong understanding of Data Warehouse/Data Mart Design, ETL, BI, OLAP, Client/Server applications.
TECHNICAL SKILLS: Data Warehousing Informatica 9.1/8.6/7.1.2 (Repository Manager, Designer, Workflow Manager, and Workflow Monitor), SSIS, Data Stage 8.x Reporting Tools Business Objects6.5, XIR3, Cognos 8 Suite Data Modeling Star-Schema Modeling, Snowflake-Schema Modeling, FACT and dimension tables, Pivot Tables, Erwin Testing Tools Win Runner, Load Runner, Test Director, Mercury Quality Center, Rational Clear Quest RDBMS Oracle 10g/9i/8i/7.x, MS SQL Server, UDB DB2 9.x, Teradata, MS Access 7.0 Programming SQL, PL/SQL, UNIX Shell Scripting, VB Script Environment Windows (95, 98, 2000, NT, XP), UNIX Other Tools TOAD, MS-Office suite (Word, Excel, Project and Outlook), BTEQ, Teradata SQL Assistant Confidential, MD Jan’ 10 – Till Date Sr.
This error is reported with three additional arguments: the file number, the block number, and an internal code indicating the type of issue with that block.
The following is an excerpt for an ORA-600 [kddummy_blkchk] error: The ORA-600 [kddummy_blkchk] error message usually reports a corruption, so to identify the object involved, first use the file number (&afn) and the block number (&bn) reported in the error message in the SQL query: The best way to resolve the corruption is to restore a copy of the affected datafile from before the error and to recover the database so these changes are applied to the restored datafile and brought forward to the current time.
You cannot determine the cause of the space leak by checking your application code, because the error is internal to Oracle Database.
You can, however, safely avoid the error by setting an event in the initialization file for your database in this form: You will also need to shut the database down and restart it to enable the event to take effect.
This error is reported with no additional arguments, as shown in the following file excerpt: The ORA-600  error often indicates an index corruption.
To identify the affected index, you’ll need to look at the trace file whose name is provided in the file, just above the error message.
Description: what is difference between ATTRIBUTE column & GLOBAL_ATTRIBUTE column in a table?
If i want to define more DFF than ATTRIBUTE column in a table then what we should do?
In this excerpt, the trace file you need to look at is called prod_ora_2367574and is located in /u01/oracle/admin/PROD/bdump.