Regla de Jira Automation cuando se fusiona una solicitud de incorporación de cambios

Depending on your Oracle installation, you may have access to one of many different versions or “modes” in which to run the SQL*Plus application.

If you wish to use SQL*Plus Command-line, you’ll simply issue the sqlplus command from your shell:

This will attempt to connect you to the default database and you’ll be prompted to enter your credentials to authenticate yourself.

In the event you need to connect to a different database or use a different user (schema), try the following, replacing your own values as necessary:

If you have access to it, you may wish to use iSQL*Plus, which is a browser-based version of the SQL*Plus command-line tool.

This is accomplished by simply visiting the iSQL*Plus URL for your database and installation. The exact URL will vary, but it is typically in the following format: http://machine_name.domain:port/isqlplus

If you’re using Windows, there is also a Windows GUI version of SQL*Plus, which can typically be launched from your start menu: Start > Programs > Oracle > Application Development > SQL Plus.

Now that you’re connected to SQL*Plus we can begin creating our file.

The first step is to configure some SQL*PLus system settings using the SET statement.

For this example, we’ll be manually altering these settings one time prior to our query and file generation, but if desired, you can change the defaults of various settings in your User Profile, located in the login.sql file.

The first few settings you typically won’t want to change, but we’ll briefly explain what each accomplishes.

• colsep is the separator character used to split your columns. For a .csv file, this is a simple comma.
• headsep is the separator character for the header row (if you require one). In this example we’re not outputting the header row, so we’ll leave this off.
• pagesize is the number of lines “per page.” This is a slightly archaic setting that is intended for printing without having too many lines per page. With a value of 0, we don’t use pages since we’re outputting to a file. If you elect to show the header row, set pagesize to a very large number (larger than the expected number of record results in the query), so your header row will only show up one time rather than once “per page.”

• trimspool set to on simply removes trailing whitespace.

Now the final two settings will need to be altered depending on your query.

• For linesize, the # value should be the total number of output columns in your resulting query.
• numwidth is the column width (number of character spaces) used when outputting numeric values.

Note: The SPOOL command is unavailable in the browser-based SQL*Plus version, iSQL*Plus. To generate files while using iSQL*Plus, change the necessary preference settings to directly output to a file.

With our settings taken care of, now we must tell SQL*Plus to output a file. This is accomplished using the SPOOL statement.

While SPOOL is active, SQL*PLus will store the output of any query to the specified file.

Therefore, the next command to enter is spool:

Skipping ahead slightly, after your query is inserted, you also need to halt spool so the file output is closed by using the spool off command:

The last step after the settings are modified and spool is running is to insert your query. For our simple example, we’re outputting all books from our books table.

Don’t forget the semi-colon to close out your query statement, then enter the aforementioned spool off command.

That’s it, you’ve generated a new text file with the results of your query using SQL*Plus.

Rather than manually entering every line, it is suggested to enter all the settings into a new script file that you can execute in SQL*Plus in a single command.

Create a new script file with the EDIT statement:

Now paste the entire script command list into your new file and save. The full contents of our example script can be found below.

To execute the script, simply use the @ symbol followed by the file name:

Your script should be executed and the .csv file created as expected.