There is one requirment where I need to login into database environment and pull all schema names into a text file ...
as of now below are the schemas available...
Now from unix script I need to fetch all these names into a file for further processing, so i wrote command like
But I am getting only below values as output.
the below are omitted
However, same script working fine on different environment(exactly configure like this environment) ..its driving me crazy...
Can anyone suggest..
Last edited by onenessboy; 08-04-2018 at 07:04 AM..
Reason: .
Hello Again,
Those that have noticed my earlier posts will know that I have succesfully installed Solaris 8 onto my pc. I haven't been able to get x-server working (i think it doesn't like my video card) though I've been able to log into root (with a bit of help from unix forums :o ) and have... (2 Replies)
telnet at my system is behaving stange. Some times I am able to telnet to other machines but sometimes it stop doing that. Then i have to reboot the machine and most of the time (not 100%) it works. SImilar is the case with SSH. Sometime it works , some time it don't. i am new to Unix and I do not... (1 Reply)
Hi,
I do have three scripts. Whcih inserts records into a table using sqlldr, creating some reprot files etc. The first script will call the second and then the second will call the third. When I run my first script from the shell prompt, all my operation are completed successfully. If I do... (23 Replies)
Hi
I've a problem with Hp-ux 11.11 9000/800/rp3440 system. Already the software for driver & its patch are loaded for HBA Fibrechannel card, but still the fibrechannel card is showing the status "Unclaimed" . What will be reason for this? How to get the status "Claimed" ?
Pl. help me out.... (4 Replies)
Hi all,
I'm trying to generate a series of txt files starting from a plain csv file
part of my code:
#!/bin/ksh
INSTALLDIR=/Users/ME/Installdir
CSV=CSV.csv
TMP=/tmp/$(basename $0).txt
tr -s "\r" "\n" < /$INSTALLDIR/$CSV > $TMP
function Makefiles
{
printf '%24s:%30s\n' "sometext"... (1 Reply)
Hi,
I'm having some trouble with an awk programme that i'm using to scan ascii files.
Unfortunately I'm not an experienced programmer but I think I am experiencing problems for a two reasons:
1) the awk was written by a PC programmer and it works on his machine, but only partly works... (10 Replies)
I am using mailx command in my script to attach a file and send an email. I need to attach a csv file and send email to a mail id -
I am using
uuencode output.csv output.csv | mailx -s "test mail" xyz@abc.com
This will send a mail with scrambled text in body.
am i missing something ?... (4 Replies)
This is the first time for using sudo for me.
# visudo
## Allows people in group admin to run all commands
%admin ALL=(ALL) ALL
# groupadd admin
# useradd temp
# usermod -a -G admin temp
# id temp
uid=506(temp) gid=506(temp) groups=506(temp),507(admin)
#
#sudo... (5 Replies)
I'm using an Ubuntu machine and expansion is not working properly. What would cause this? Do I need to check for any particular bash packages?
$ ipcs -m | grep $USER | awk '{printf "%s ",$2}'
$ ipcs -m | grep UNF | awk '{printf "%s ",$2}'
294912 1048577 425986 688131 786436 1245189... (14 Replies)
Discussion started by: cokedude
14 Replies
LEARN ABOUT SUSE
create_schema
CREATE SCHEMA(7) SQL Commands CREATE SCHEMA(7)NAME
CREATE SCHEMA - define a new schema
SYNOPSIS
CREATE SCHEMA schemaname [ AUTHORIZATION username ] [ schema_element [ ... ] ]
CREATE SCHEMA AUTHORIZATION username [ schema_element [ ... ] ]
DESCRIPTION
CREATE SCHEMA enters a new schema into the current database. The schema name must be distinct from the name of any existing schema in the
current database.
A schema is essentially a namespace: it contains named objects (tables, data types, functions, and operators) whose names can duplicate
those of other objects existing in other schemas. Named objects are accessed either by ``qualifying'' their names with the schema name as a
prefix, or by setting a search path that includes the desired schema(s). A CREATE command specifying an unqualified object name creates the
object in the current schema (the one at the front of the search path, which can be determined with the function current_schema).
Optionally, CREATE SCHEMA can include subcommands to create objects within the new schema. The subcommands are treated essentially the same
as separate commands issued after creating the schema, except that if the AUTHORIZATION clause is used, all the created objects will be
owned by that user.
PARAMETERS
schemaname
The name of a schema to be created. If this is omitted, the user name is used as the schema name. The name cannot begin with pg_, as
such names are reserved for system schemas.
username
The name of the user who will own the schema. If omitted, defaults to the user executing the command. Only superusers can create
schemas owned by users other than themselves.
schema_element
An SQL statement defining an object to be created within the schema. Currently, only CREATE TABLE, CREATE VIEW, CREATE INDEX, CREATE
SEQUENCE, CREATE TRIGGER and GRANT are accepted as clauses within CREATE SCHEMA. Other kinds of objects may be created in separate
commands after the schema is created.
NOTES
To create a schema, the invoking user must have the CREATE privilege for the current database. (Of course, superusers bypass this check.)
EXAMPLES
Create a schema:
CREATE SCHEMA myschema;
Create a schema for user joe; the schema will also be named joe:
CREATE SCHEMA AUTHORIZATION joe;
Create a schema and create a table and view within it:
CREATE SCHEMA hollywood
CREATE TABLE films (title text, release date, awards text[])
CREATE VIEW winners AS
SELECT title, release FROM films WHERE awards IS NOT NULL;
Notice that the individual subcommands do not end with semicolons.
The following is an equivalent way of accomplishing the same result:
CREATE SCHEMA hollywood;
CREATE TABLE hollywood.films (title text, release date, awards text[]);
CREATE VIEW hollywood.winners AS
SELECT title, release FROM hollywood.films WHERE awards IS NOT NULL;
COMPATIBILITY
The SQL standard allows a DEFAULT CHARACTER SET clause in CREATE SCHEMA, as well as more subcommand types than are presently accepted by
PostgreSQL.
The SQL standard specifies that the subcommands in CREATE SCHEMA can appear in any order. The present PostgreSQL implementation does not
handle all cases of forward references in subcommands; it might sometimes be necessary to reorder the subcommands in order to avoid forward
references.
According to the SQL standard, the owner of a schema always owns all objects within it. PostgreSQL allows schemas to contain objects owned
by users other than the schema owner. This can happen only if the schema owner grants the CREATE privilege on his schema to someone else.
SEE ALSO
ALTER SCHEMA [alter_schema(7)], DROP SCHEMA [drop_schema(7)]
SQL - Language Statements 2010-05-14 CREATE SCHEMA(7)