Formatting issue in csv file

Question

set echo off
--set line 999
set space 0
set feedback on
set term off
set linesize 32000
set pagesize 49999
set colsep ,
select ci.CIRC_HUM_ID as Circuit_id,
        cp.CIRC_PATH_HUM_ID as Associated_Path,
        ci.TYPE as Category,
        ci.bandwidth,
        ci.VENDOR,
        ci.STATUS,
        si.CLLI as A_Site,
        si.ADDRESS as A_Site_Address,
        si.CITY as A_Site_City,
        si.STATE_PROV as A_Site_State,
        si1.CLLI as Z_Site,
        si1.ADDRESS as Z_Site_Address,
        si1.CITY as Z_Site_City,
        si1.STATE_PROV as Z_Site_State
from telepac1.circ_path_inst cp
     ,telepac1.site_inst si
     ,telepac1.site_inst si1
     ,telepac1.circ_inst ci
where si.site_inst_id = cp.A_SIDE_SITE_ID
and si1.site_inst_id = cp.Z_SIDE_SITE_ID
and cp.CIRC_PATH_INST_ID = ci.CIRC_PATH_INST_ID (+);I am getting correct data in csv format but for Z_Site_Address some the vales of cell are coming to next row.
Z_Site_Address
SBC
345 N San Joaquin      the data is coming is like this for few rows
but i want data like below
Z_Site_Address
SBC 345 N San Joaquin

Answer 1

>
I am getting correct data in csv format but for Z_Site_Address some the vales of cell are coming to next row.
Z_Site_Address
SBC
345 N San JoaquinThat is because, as Jeneesh said, your data has embedded record delimiters. That data above may LOOK wrong but it is EXACTLY what your column contained.
That often happens when an application uses a MEMO field that lets a user type in multiple lines for a long text description or, in your case, for an address.
If you don't want embedded record delmiters in your DB data you should remove them when your app saves the data to begin with. If you convert those characters to spaces in the file and load the file again you will NOT have the same content you have to begin with. That means that app field will display one long line of characters to the user.
That is the price you pay for using delimited files; by default any embedded delimiters will cause the created file to be unloadable.
Be aware that if you are creating a COMMA delimited file then any embedded commas can cause a problem also unless the field is enclosed in double quotes. That is because when you read or try to load the file those 'extra' comma will be interpreted as a FIELD separator.
For example an address like '123 Maple St, Apt 111' will appear to be TWO values: '123 Maple St' and 'Apt 111'.