Sponsored Content
Top Forums Shell Programming and Scripting Read Table,View,Package,Function and Procedure Name in a File Post 302458229 by hanu_oracle on Thursday 30th of September 2010 06:12:11 AM
Old 09-30-2010
[/COLOR]
Quote:
Originally Posted by sboss
Hi

I am new to Unix shell scripting. But i need help to slove the below issue.

Issue description:
I want to read table, view names and package names in a file

my plan to find the table name is : search "From" key word find the table or view
To find the packge name : Search "Package body" key word
To Search Function Name: Search "Function"

In a file i have multiple queries like below.

Sample file:

select * from EMP,DEPT
where emp.deptno=dept.deptno

Package Body xxx_Search_PKG

In the above query i want to find the EMP table first display out as below in a file. find DEPT table and put in second line.

Output: Find each table or Function or Package and display out put like below in one file.

<file Name> <0000> <table name/package name/function name> <Report> <APPS>



Thanks in Advance
If u have Database access, you can simply fetch details using:
select OBJECT_NAME, OBJECT_TYPE from dba_objects where OBJECT_TYPE in ('TABLE', 'VIEW', 'PROCEDURE', 'PACKAGE') order by OBJECT_TYPE;

In the Unix every thing is case sensitive,
In sql query you can write the query as "FROM table_name WHERE" or "from table_name where" or "From table_name Where" and so on formats.

Some times you are using the Multiple Object names in the select query with alias names also.

select a.col1, a.col2, b.col1, d.col5 from TABLE1 a, Table2 b, table4 d
where ....

It is some more difficult to fetch the all the object details in the file.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

procedure/function not found in .ksh

Hi all , I am getting an error "job_procfile not found" while excecuting a .ksh script. The script is used to create control-m ( scheduler ) jobs dynamically by reading parameter files ( flat filescomma seperated ) job_procfile is a function within the .ksh script The script is something... (8 Replies)
Discussion started by: rajesh_ramaoz
8 Replies

2. Programming

how to view symbol table in unix

hi , How to view the contents of a "c" program symbol table information in unix. (1 Reply)
Discussion started by: saravanan_nitt
1 Replies

3. Programming

Cannot read a file with read(fd, buffer, buffersize) function

# include <stdio.h> # include <fcntl.h> # include <stdlib.h> # include <sys/stat.h> int main(int argc, char *argv) { int fRead, fPadded, padVal; int btRead; int BUFFSIZE = 512; char buff; if (argc != 4) { printf ("Please provide all of the... (3 Replies)
Discussion started by: naranja18she
3 Replies

4. Shell Programming and Scripting

loading the data to the partitioned table using procedure

Hi one help, I need one procedure to load data from flat file to table. Table name as input parameter for the procedure. can anyone help me Thanks, Raj, (1 Reply)
Discussion started by: easterraj
1 Replies

5. UNIX and Linux Applications

create table via stored procedure (passing the table name to it)

hi there, I am trying to create a stored procedure that i can pass the table name to and it will create a table with that name. but for some reason it creates with what i have defined as the variable name . In the case of the example below it creates a table called 'tname' for example ... (6 Replies)
Discussion started by: rethink
6 Replies

6. Shell Programming and Scripting

Read parameter file in a shell script to unload a DB2 Table???

Hi , I Have following requirement: DB2 Sql query to pass from a parameter file for example, I would create a parameter file with (SELECT column 1, column 2 FROM Table name) then job would read it and create a file with the contents named table.txt How to write/modify below ksh script to... (10 Replies)
Discussion started by: developer.dwh9
10 Replies

7. Shell Programming and Scripting

Table or view is not exist

If I select the statement on db is ok, but same statement on UNIX script I get table or view is not exist. what should I do?:( (5 Replies)
Discussion started by: Hscript
5 Replies

8. UNIX for Beginners Questions & Answers

Improving find to read table name from file

Hi there, I currently use the following find command to recursively search all the subdirectories in our file system for a table ( in this case BB_TENURE_DAYS) find -type f -exec grep -l "BB_TENURE_DAYS" {} \+ So I have this so far - the problem is how do I read the line to get the... (2 Replies)
Discussion started by: rjsha1
2 Replies

9. UNIX for Beginners Questions & Answers

Read Table in file and split

HELLO I need your help please , i need to read a file that contain a table like : Name | Status ------------------ DB 1 | UP DB 2 | UP DB 3 | DOWN DB 4 | UP DB 5 | UP the objective to read each line and check if DB is UP or Down and give me the name of Down database.... (10 Replies)
Discussion started by: Abdellah
10 Replies
CREATE TABLE 
AS(7) PostgreSQL 9.2.7 Documentation CREATE TABLE AS(7) NAME
CREATE_TABLE_AS - define a new table from the results of a query SYNOPSIS
CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE table_name [ (column_name [, ...] ) ] [ WITH ( storage_parameter [= value] [, ... ] ) | WITH OIDS | WITHOUT OIDS ] [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ] [ TABLESPACE tablespace_name ] AS query [ WITH [ NO ] DATA ] DESCRIPTION
CREATE TABLE AS creates a table and fills it with data computed by a SELECT command. The table columns have the names and data types associated with the output columns of the SELECT (except that you can override the column names by giving an explicit list of new column names). CREATE TABLE AS bears some resemblance to creating a view, but it is really quite different: it creates a new table and evaluates the query just once to fill the new table initially. The new table will not track subsequent changes to the source tables of the query. In contrast, a view re-evaluates its defining SELECT statement whenever it is queried. PARAMETERS
GLOBAL or LOCAL Ignored for compatibility. Use of these keywords is deprecated; refer to CREATE TABLE (CREATE_TABLE(7)) for details. TEMPORARY or TEMP If specified, the table is created as a temporary table. Refer to CREATE TABLE (CREATE_TABLE(7)) for details. UNLOGGED If specified, the table is created as an unlogged table. Refer to CREATE TABLE (CREATE_TABLE(7)) for details. table_name The name (optionally schema-qualified) of the table to be created. column_name The name of a column in the new table. If column names are not provided, they are taken from the output column names of the query. WITH ( storage_parameter [= value] [, ... ] ) This clause specifies optional storage parameters for the new table; see Storage Parameters for more information. The WITH clause can also include OIDS=TRUE (or just OIDS) to specify that rows of the new table should have OIDs (object identifiers) assigned to them, or OIDS=FALSE to specify that the rows should not have OIDs. See CREATE TABLE (CREATE_TABLE(7)) for more information. WITH OIDS, WITHOUT OIDS These are obsolescent syntaxes equivalent to WITH (OIDS) and WITH (OIDS=FALSE), respectively. If you wish to give both an OIDS setting and storage parameters, you must use the WITH ( ... ) syntax; see above. ON COMMIT The behavior of temporary tables at the end of a transaction block can be controlled using ON COMMIT. The three options are: PRESERVE ROWS No special action is taken at the ends of transactions. This is the default behavior. DELETE ROWS All rows in the temporary table will be deleted at the end of each transaction block. Essentially, an automatic TRUNCATE(7) is done at each commit. DROP The temporary table will be dropped at the end of the current transaction block. TABLESPACE tablespace_name The tablespace_name is the name of the tablespace in which the new table is to be created. If not specified, default_tablespace is consulted, or temp_tablespaces if the table is temporary. query A SELECT(7), TABLE, or VALUES(7) command, or an EXECUTE(7) command that runs a prepared SELECT, TABLE, or VALUES query. WITH [ NO ] DATA This clause specifies whether or not the data produced by the query should be copied into the new table. If not, only the table structure is copied. The default is to copy the data. NOTES
This command is functionally similar to SELECT INTO (SELECT_INTO(7)), but it is preferred since it is less likely to be confused with other uses of the SELECT INTO syntax. Furthermore, CREATE TABLE AS offers a superset of the functionality offered by SELECT INTO. Prior to PostgreSQL 8.0, CREATE TABLE AS always included OIDs in the table it created. As of PostgreSQL 8.0, the CREATE TABLE AS command allows the user to explicitly specify whether OIDs should be included. If the presence of OIDs is not explicitly specified, the default_with_oids configuration variable is used. As of PostgreSQL 8.1, this variable is false by default, so the default behavior is not identical to pre-8.0 releases. Applications that require OIDs in the table created by CREATE TABLE AS should explicitly specify WITH (OIDS) to ensure desired behavior. EXAMPLES
Create a new table films_recent consisting of only recent entries from the table films: CREATE TABLE films_recent AS SELECT * FROM films WHERE date_prod >= '2002-01-01'; To copy a table completely, the short form using the TABLE command can also be used: CREATE TABLE films2 AS TABLE films; Create a new temporary table films_recent, consisting of only recent entries from the table films, using a prepared statement. The new table has OIDs and will be dropped at commit: PREPARE recentfilms(date) AS SELECT * FROM films WHERE date_prod > $1; CREATE TEMP TABLE films_recent WITH (OIDS) ON COMMIT DROP AS EXECUTE recentfilms('2002-01-01'); COMPATIBILITY
CREATE TABLE AS conforms to the SQL standard. The following are nonstandard extensions: o The standard requires parentheses around the subquery clause; in PostgreSQL, these parentheses are optional. o In the standard, the WITH [ NO ] DATA clause is required; in PostgreSQL it is optional. o PostgreSQL handles temporary tables in a way rather different from the standard; see CREATE TABLE (CREATE_TABLE(7)) for details. o The WITH clause is a PostgreSQL extension; neither storage parameters nor OIDs are in the standard. o The PostgreSQL concept of tablespaces is not part of the standard. Hence, the clause TABLESPACE is an extension. SEE ALSO
CREATE TABLE (CREATE_TABLE(7)), EXECUTE(7), SELECT(7), SELECT INTO (SELECT_INTO(7)), VALUES(7) PostgreSQL 9.2.7 2014-02-17 CREATE TABLE AS(7)
All times are GMT -4. The time now is 06:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy