SQL> set linesize 120SQL> col file_name for a40SQL> col tablespace_name for a20

select file_name,tablespace_name from dba_data_fileswhere tablespace_name in ( select tablespace_name from dba_tablespaces where contents not in 'TEMPORARY')

FILE_NAME                                TABLESPACE_NAME---------------------------------------- --------------------/oradata/ora9test/system01.dbf           SYSTEM/oradata/ora9test/undotbs01.dbf          UNDOTBS1/oradata/ora9test/drsys01.dbf            DRSYS/oradata/ora9test/example01.dbf          EXAMPLE/oradata/ora9test/indx01.dbf             INDX/oradata/ora9test/tools01.dbf            TOOLS/oradata/ora9test/users01.dbf            USERS/oradata/ora9test/xdb01.dbf              XDB

8 rows selected.

set linesize 120col file_name for a40col tablespace_name for a20

This is a test from the ECTO blog client.

When doing search and replace in vi, there is no need to ‘escape’ forward slash characters ‘/’ when manipulating pathnames. Instead, simply change the character used to delimit the search terms to something other than ‘/’ directly within vi (no .exrc change needed).

e.g.

./.cpan/build/Archive-Tar-1.30./.cpan/build/Archive-Tar-1.30/bin./.cpan/build/Archive-Tar-1.30/bin/ptar./.cpan/build/Archive-Tar-1.30/bin/ptardiff./.cpan/build/Archive-Tar-1.30/blib./.cpan/build/Archive-Tar-1.30/blib/arch

Then use the string below which uses ‘?’ where usually a ‘/’ is used to separate and delimit the srearch & replace terms. In this example I am replacing …cpan/build… with …cpan/build/z/y/z…

:%s?cpan/build?cpan/build/z/y/z?

Which results in

./.cpan/build/x/y/z/Archive-Tar-1.30./.cpan/build/x/y/x/Archive-Tar-1.30/bin./.cpan/build/x/y/x/Archive-Tar-1.30/bin/ptar./.cpan/build/x/y/x/Archive-Tar-1.30/bin/ptardiff./.cpan/build/x/y/x/Archive-Tar-1.30/blib./.cpan/build/x/y/x/Archive-Tar-1.30/blib/arch