Extending What STORE OffersĪs an extension to what STORE offers with respect to settings, you can also add in column format settings (i.e., "col object_name format a20"). Create a SQL file (defaultenv or a one off "reset" file) with the normal values set, and then call it at the SQL prompt. To reset your session settings, you can explicitly reset these parameters in a script, but that introduces unnecessary code and maintenance effort. Six SET commands can be used to produce a "clean" header and footer for an output file. If in an extract, transform, and load (ETL) environment, it is very common to spool out the contents of a table (or query) into a delimited file. A practical reason to use a separate settings file is to keep reports versus non-reports settings separate (one script sets them and the other unsets them). If you can store your favorite SQL*Plus settings in a separate file, why not re-purpose your login.sql file by adding all of the non-default settings you prefer? You certainly can, but if your login.sql script outputs anything (I have mine output the user and name of the database), you will get that output as well. All of the settings with "(hex xx)" are the same, except that SHOW ALL displays the value's corresponding hex value (how does that help?). Some of the differences are informational in nature. Ttitle OFF and is the first few characters of the next SELECT statement appinfo is OFF and set to "SQL*Plus"ītitle OFF and is the first few characters of the next SELECT statement The differences (virtually all are in what SHOW ALL displays) are shown below. Around line 50, the value for "suffix" is "sql." Given that the default suffix is "sql," then all that was need before is simply "STORE SET defaultenv." One other difference that may stand out between the output of show all and the contents of defaultenv is the number of lines. The first thing you should notice is that every line in the file is preceded by a "set" command. Is the "dot sql" at the end necessary? Using a text editor, let's open defaultenv.sql and see. If on UNIX, the case of "defaultenv" does matter. STORE and SET are capitalized only to point out their special meaning, otherwise, case does not matter for these words. One Step Beyond SET: Using STOREįrom the SQL*Plus® User's Guide and Reference (Release 10.2) guide, the purpose of the STORE command is to save "attributes of the current SQL*Plus environment in a script." Start up SQL*Plus and then immediately enter STORE SET defaultenv.sql at the SQL prompt. Short of logging out and restarting SQL*Plus, or taking the time to reset all of the SET commands, is there an easier way to restore your favorite or preferred session settings? The good news is that the answer is yes, and even better news is that this is very easy to perform. If you have written a script to produce output from a query, chances are pretty good you have also added one or more SET commands to format the output. Instead of just showing these settings, SQL*Plus offers a way to quickly set and customize them. The SHOW command works the same in both UNIX and Windows environments, and SHOW ALL can be used to display the settings or values of nearly 70 items. Beyond that, adjust your expectations of what you think it means to use a command line.SQL*Plus offers several handy features you can use to control your SQL*Plus session. Going back to my first statement, prove that sqlplus is not installed. Is my IT people are installing the s/w on the client now how can i again do the installation ? give me other option plz But you haven't gotten far enough to deal with that.īut my prod. And there is nothing to "configure" except for the network connectivity. You can think, but I know that unless the person doing the installation did something tricky, sqlplus is installed by default. I think for client oracle installation we will not get SQL*Pluse tool. Even your "white screen" is just a command prompt. It is inherently impossible to use it any other way except "at a command prompt". I more like to working in oracle SQL*Pluse instead of cmd prompt. At a command prompt (yes you need to work at a command prompt) go to your ORACLE_HOME\bin directory and do a "dir sql*.exe". What do you mean "i am not about to see Oracle SQL*Plus"? Just go to your ORACLE_HOME/bin directory. I am using client oracle software in that i am not about see Oracle SQL*Pluse
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |