Huge Records

Friends,
500 Million Records,Client wants Ad-Hoc reporting.Is it possible with Essbase?

Mehmet,
I will have to disagree with you slightly.
I would answer that it depends. 50 million recodrs could result in a much smaller database becaue everything is intersections. Think about a block storage DB where time and accounts are dense. If each record had one account and one time period, then it would condense down quite a bit. That said, I'll guess this is not the case, and without knowing more about the data, it is difficult if not impossible to answer you

Similar Messages

Huge records retrieve

Hi,
I have a requirement to fetch the huge records from prod DB.
Select query forming charter length is more than 10000, but command allows to execute only <2499 charters length.
How could resolve this.
Query eg:
Select column1, column2, column3,column4 from where (some join condition) AND (id='xxxx' OR id ='xxx' etc)

As suggested already you can use external table.
Here is an example using EMP table from SCOTT schema.
Following is a sample file in which i have list of empno
SQL> !cat test.txt
7369
7499
7521
7566
7654
7698
7782
7788
7839
7844
7876The file is in the following directory
SQL> !pwd
/homeNow i create a Oracle directory object for the above directory.
SQL> create directory test_dir as '/home'
2 /
Directory created.Now i create a external table to query the file test.txt
SQL> create table test_et
2 (
3    empno integer
4 )
5 organization external
6 (
7    default directory test_dir
8    access parameters
9    (
10      records delimited by newline
11    )
12    location
13    (
14      'test.txt'
15    )
16 )
17 /
Table created.Now you can query the external table like this. It will pick up the data from test.txt
SQL> select * from test_et;
     EMPNO
      7369
      7499
      7521
      7566
      7654
      7698
      7782
      7788
      7839
      7844
      7876
11 rows selected.Now i can use it in my WHERE clause like this.
SQL> select * from emp where empno in (select empno from test_et);
     EMPNO ENAME JOB              MGR HIREDATE         SAL        COM     DEPTNO
      7369 SMITH CLERK           7902 02-APR-81       2975          0         20
      7499 ALLEN SALESMAN        7698 20-FEB-81       1600        300         30
      7521 WARD   SALESMAN        7698 22-FEB-81       1250        500         30
      7566 JONES MANAGER         7839 02-APR-81       2975          0         20
      7654 MARTIN SALESMAN        7698 28-SEP-81       1250       1400         30
      7698 BLAKE MANAGER         7839 01-MAY-81       2850          0         30
      7782 CLARK MANAGER         7839 09-JUN-81       2450          0         10
      7788 SCOTT ANALYST         7566 19-APR-87       3000          0         20
      7839 KING   PRESIDENT            17-NOV-81       5000          0         10
      7844 TURNER SALESMAN        7698 08-SEP-81       1500          0         30
      7876 ADAMS CLERK           7788 23-MAY-87       1100          0         20
11 rows selected.
SQL>

Program times out while looping at internal table with huge records - Needs fine tuning suggestions

Hi,
I am trying to execute a report. It times out while looping at vbap internal table. This internal table has 140000 records and does the validation within this loop and geenrates data for the output. Due to this huge volume, the program times out when executed foreground.
There are no nested loops, so I cannot apply 'Parallel Cursor' here.
Is there any way I can fine tune the program so that it doesn't timeout? Is it possible to apply 'Parallel Processing' . If yes, how?
Thanks,
Pavan

Hi Pavan ,
              ->sort your internal table by all primary key for vbap.
              ->Read a Record from the table (use your condition here)
              ->if record satisfys your where condition ,get that record index .
              ->loop the table from the index (without condition) .
              its like parallel cursor only but for single loop .;-)
              ->use field symbols ,wherever possible .
           if still dump is coming ,contact your basis team .
regards,
Krishna.

How to Handle Huge record count in JDBC

Hi,
Can we process 20 lakhs records which would size near to 136 MB using JDBC sender channel in a single call and the same need to deliver to Target system which is JDBC too.
Kindly mention which way this can be achieved.
Regards

Hi Venkata,
Kindly go through this below link to processing the huge amount of data from the sender JDBC.
http://scn.sap.com/people/peng.shen2/blog/2009/12/23/pi-how-to-handle-high-volume-data-per-jdbc-adapter
https://scn.sap.com/thread/2005124
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/09/24/jdbc-receiver-scenarios-best-practices--how-to-handle-high-volume-load-stored-procedure-design-part6
Best Regards,
Monikandan.

Can xcelsius handle huge records in excel?

I read the doc and it say no limit but I see some slowness and sometime the range won't even take affect. I created an excel pulling from sql server which has 7500 rows, I want to do a combo box on all of these, is there a way around this? since i dont see an
option to pull from database.

Hi cssanangeles:
In theory, there will be no limit for the binding excel range, but the performance will decrease depends on the increases of binding excel records. You can also configure the u201CMaximum Limits Of Rowsu201D under u201CFile->Preference->Excel Optionu201D (the default suggested rows is u201C512u201D)
For you question you want to retrieve thousands of rows data from SQL server then binds these data to Combo Box. I can give you some suggestions:
1.Write a web service to retrieve data from sql server, then use Xcelsius u201Cweb service connectionu201D under u201CManage Connectionu201D section to consume the service and get the data from sql server to spread sheet.
2.If you use sql server 2005, you can use u201CReporting Serviceu201D to generate service for your data base, also then consume the data using Xcelsius u201CWeb Service Connectionu201D and do the same steps like previous option.
3.Xcelsius also provide you a tool to generate web service with easy way (without coding).
Using flynet, you can get flynet installation file under Xcelsius installation folder u201CXcelsius\Connectivity\Flynet Webservice Generatoru201D for more information about flynet please refer to
http://myxcelsius.com/2008/11/07/generating-web-services-for-xcelsius-using-flynet-web-service-generator/
Hope it helps with your work! And let me know if you need any further help:)
Thanks!
Bill

Rollbacking huge records

Hi,
we are getting a daily feed of 7 million records and need to be inserted to the oracle table.
After loading we identified that there were some issues in the data loaded and want to load new 7 milllion records.
a)first of all, database design should not allow incorrect data to be inserted.
b)After inserting due to design flaw, how we can rollback and insert new 7 million records?
Whats the best way to achieve that rather than going for a delete statement.
The table is partitioned based on month.
Thanks

Pandeesh wrote:
Hi,
we are getting a daily feed of 7 million records and need to be inserted to the oracle table.
After loading we identified that there were some issues in the data loaded and want to load new 7 milllion records.
a)first of all, database design should not allow incorrect data to be inserted.What determines "correct"?
>
b)After inserting due to design flaw, how we can rollback and insert new 7 million records?You can not ROLLBACK any data that has been COMMITTED.
>
Whats the best way to achieve that rather than going for a delete statement.How do you unring the bell?
>
The table is partitioned based on month.SO?

Display records from database table

My database table has 495K records i want to display them all in se11 tcode and than download into excel ...but because of huge records it timeout.
Do I need to write a program for this?
Or is there any other smarter way.
Regards,
DNP

Hi,
Please follow the steps below:
1. Go to the selection screen of SE11 and provide your selection criteria (if required).
2. Click on Settings menu->User parameters->ALV Grid display.
3. Now click on Program menu->Execute in background->Provide output device name as LP01 or LOCAL or any valid printer parameters->Click continue->Click Immediate button->Click Save.
4. You can see the background job for this in SM37.
5. Once the background job is completed, it will appear in gleen color.
6. Click on the completed job and then click on Spool button.
7. Once the output is displayed in spool you can now easily download it to excel by clicking on System menu->List->Save->Local File.
Hope this will help you.
Regards,
Venkat

Issue of grouping IDOC segments in huge loads

Hi All,
My Scenario is File to IDoc. No problem in posting IDoc in R3. But when i see the Idoc structure in R3, all the data records are grouped in different segements as seen below:-
This is how i see in we05.
IDoc No (00000000001234)
- Control Rec.
- Segments 000001 to 001000
- S01 Segment 000001 (Actual records)
- S02 Segment 000002
- S03 Segment 000003
- Segments 001001 to 001001
- S04 Segment 000004
- S05 Segment 000005
- S06 Segment 000006
- Status Rec.
I dont want the grouping of Idoc segments to take place. It should be under same data segment.
Please provide me your valuable solutions to resolve the same.
Note: This problem occurs only when processing huge records.
Thanks in advance,

Hi Sriram,
It is the standard program flow of transaction WE02 which checks the number of segments.if the count is more than 1000,it creates a another group and displays it for the sake of readability.
Anyway it does not affect the inbound processing of the IDOC.
Thank you.
Regards,
Karun.M

BPC NW 7.0: Limit of records in Application

Hello Experts,
I have heard that there is a limit of records in BPC application (I mean fact table records) till 4 millions records. Is it true? What happens if this limit will be exceeded?
Thanks in advance.

Hi Yulia,
I dont think there is any limitations on records in BPC. But yes, if there are huge records, then the performance to tool decreases and it takes loads of time in page opening, optimizing, sending data and also in displaying reports.
Therefore, it is suggested to keep data records minimum as per your requirement.
Hope this clarifies your question.
Rgds,
Poonam

SQL Query to fetch records from tables which have 75+ million records

Hi,
I have the explain plan for a sql stmt.Require your suggestions to improve this.
PLAN_TABLE_OUTPUT
| Id | Operation                            | Name                         | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT                     |                              |   340 |   175K| 19075 |
|   1 | TEMP TABLE TRANSFORMATION           |                              |       |       |       |
|   2 |   LOAD AS SELECT                     |                              |       |       |       |
|   3 |    SORT GROUP BY                     |                              |    32M| 1183M|   799K|
|   4 |     TABLE ACCESS FULL                | CLM_DETAIL_PRESTG            |   135M| 4911M|   464K|
|   5 |   LOAD AS SELECT                     |                              |       |       |       |
|   6 |    TABLE ACCESS FULL                 | CLM_HEADER_PRESTG            |     1 |   274 |   246K|
PLAN_TABLE_OUTPUT
|   7 |   LOAD AS SELECT                     |                              |       |       |       |
|   8 |    SORT UNIQUE                       |                              |   744K|    85M| 8100 |
|   9 |     TABLE ACCESS FULL                | DAILY_PROV_PRESTG            |   744K|    85M| 1007 |
| 10 |   UNION-ALL                          |                              |       |       |       |
| 11 |    SORT UNIQUE                       |                              |   177 | 97350 | 9539 |
| 12 |     HASH JOIN                        |                              |   177 | 97350 | 9538 |
| 13 |      HASH JOIN OUTER                 |                              |     3 | 1518 | 9533 |
| 14 |       HASH JOIN                      |                              |     1 |   391 | 8966 |
| 15 |        TABLE ACCESS BY INDEX ROWID   | CLM_DETAIL_PRESTG            |     1 |    27 |     3 |
| 16 |         NESTED LOOPS                 |                              |     1 |   361 |    10 |
| 17 |          NESTED LOOPS OUTER          |                              |     1 |   334 |     7 |
PLAN_TABLE_OUTPUT
| 18 |           NESTED LOOPS OUTER         |                              |     1 |   291 |     4 |
| 19 |            VIEW                      |                              |     1 |   259 |     2 |
| 20 |             TABLE ACCESS FULL        | SYS_TEMP_0FD9D66C9_DA2D01AD |     1 |   269 |     2 |
| 21 |            INDEX RANGE SCAN          | CLM_PAYMNT_CLMEXT_PRESTG_IDX |     1 |    32 |     2 |
| 22 |           TABLE ACCESS BY INDEX ROWID| CLM_PAYMNT_CHKEXT_PRESTG     |     1 |    43 |     3 |
| 23 |            INDEX RANGE SCAN          | CLM_PAYMNT_CHKEXT_PRESTG_IDX |     1 |       |     2 |
| 24 |          INDEX RANGE SCAN            | CLM_DETAIL_PRESTG_IDX        |     6 |       |     2 |
| 25 |        VIEW                          |                              |    32M|   934M| 8235 |
| 26 |         TABLE ACCESS FULL            | SYS_TEMP_0FD9D66C8_DA2D01AD |    32M|   934M| 8235 |
| 27 |       VIEW                           |                              |   744K|    81M|   550 |
| 28 |        TABLE ACCESS FULL             | SYS_TEMP_0FD9D66CA_DA2D01AD |   744K|    81M|   550 |
PLAN_TABLE_OUTPUT
| 29 |      TABLE ACCESS FULL               | CCP_MBRSHP_XREF              | 5288 |   227K|     5 |
| 30 |    SORT UNIQUE                       |                              |   163 | 82804 | 9536 |
| 31 |     HASH JOIN                        |                              |   163 | 82804 | 9535 |
| 32 |      HASH JOIN OUTER                 |                              |     3 | 1437 | 9530 |
| 33 |       HASH JOIN                      |                              |     1 |   364 | 8963 |
| 34 |        NESTED LOOPS OUTER            |                              |     1 |   334 |     7 |
| 35 |         NESTED LOOPS OUTER           |                              |     1 |   291 |     4 |
| 36 |          VIEW                        |                              |     1 |   259 |     2 |
| 37 |           TABLE ACCESS FULL          | SYS_TEMP_0FD9D66C9_DA2D01AD |     1 |   269 |     2 |
| 38 |          INDEX RANGE SCAN            | CLM_PAYMNT_CLMEXT_PRESTG_IDX |     1 |    32 |     2 |
| 39 |         TABLE ACCESS BY INDEX ROWID | CLM_PAYMNT_CHKEXT_PRESTG     |     1 |    43 |     3 |
PLAN_TABLE_OUTPUT
| 40 |          INDEX RANGE SCAN            | CLM_PAYMNT_CHKEXT_PRESTG_IDX |     1 |       |     2 |
| 41 |        VIEW                          |                              |    32M|   934M| 8235 |
| 42 |         TABLE ACCESS FULL            | SYS_TEMP_0FD9D66C8_DA2D01AD |    32M|   934M| 8235 |
| 43 |       VIEW                           |                              |   744K|    81M|   550 |
| 44 |        TABLE ACCESS FULL             | SYS_TEMP_0FD9D66CA_DA2D01AD |   744K|    81M|   550 |
| 45 |      TABLE ACCESS FULL               | CCP_MBRSHP_XREF              | 5288 |   149K|     5 |
The CLM_DETAIL_PRESTG table has 100 million records and the CLM_HEADER_PRESTG table has 75 million records.
Any gussestions on how to getch huge records from tables of this size will help.
Regards,
Narayan

WITH CLAIM_DTL
     AS ( SELECT
                  ICN_NUM,
MIN (FIRST_SRVC_DT) AS FIRST_SRVC_DT,
MAX (LAST_SRVC_DT) AS LAST_SRVC_DT,
MIN (PLC_OF_SRVC_CD) AS PLC_OF_SRVC_CD
FROM CCP_STG.CLM_DETAIL_PRESTG CD WHERE ACT_CD <>'D'
GROUP BY ICN_NUM),
CLAIM_HDR
     AS (SELECT
                ICN_NUM,
SBCR_ID,
MBR_ID,
MBR_FIRST_NAME,
MBR_MI,
MBR_LAST_NAME,
MBR_BIRTH_DATE,
GENDER_TYPE_CD,
SBCR_RLTNSHP_TYPE_CD,
SBCR_FIRST_NAME,
SBCR_MI,
SBCR_LAST_NAME,
SBCR_ADDR_LINE_1,
SBCR_ADDR_LINE2,
SBCR_ADDR_CITY,
SBCR_ADDR_STATE,
SBCR_ZIP_CD,
PRVDR_NUM,
CLM_PRCSSD_DT,
CLM_TYPE_CLASS_CD,
AUTHO_NUM,
TOT_BILLED_AMT,
HCFA_DRG_TYPE_CD,
FCLTY_ADMIT_DT,
ADMIT_TYPE,
DSCHRG_STATUS_CD,
FILE_BILLING_NPI,
CLAIM_LOCATION_CD,
CLM_RELATED_ICN_1,
SBCR_ID||0
|| MBR_ID
|| GENDER_TYPE_CD
|| SBCR_RLTNSHP_TYPE_CD
|| MBR_BIRTH_DATE
AS MBR_ENROLL_ID,
SUBSCR_INSGRP_NM ,
CAC,
PRVDR_PTNT_ACC_ID,
BILL_TYPE,
PAYEE_ASSGN_CODE,
CREAT_RUN_CYC_EXEC_SK,
PRESTG_INSRT_DT
FROM CCP_STG.CLM_HEADER_PRESTG P WHERE ACT_CD <>'D' AND SUBSTR(CLM_PRCSS_TYPE_CD,4,1) NOT IN ('1','2','3','4','5','6') ),
PROV AS ( SELECT DISTINCT
PROV_ID,
PROV_FST_NM,
PROV_MD_NM,
PROV_LST_NM,
PROV_BILL_ADR1,
PROV_BILL_CITY,
PROV_BILL_STATE,
PROV_BILL_ZIP,
CASE WHEN PROV_SEC_ID_QL='E' THEN PROV_SEC_ID
ELSE NULL
END AS PROV_SEC_ID,
PROV_ADR1,
PROV_CITY,
PROV_STATE,
PROV_ZIP
FROM CCP_STG.DAILY_PROV_PRESTG),
MBR_XREF AS (SELECT SUBSTR(MBR_ENROLL_ID,1,17)||DECODE ((SUBSTR(MBR_ENROLL_ID,18,1)),'E','1','S','2','D','3')||SUBSTR(MBR_ENROLL_ID,19) AS MBR_ENROLLL_ID,
NEW_MBR_FLG
FROM CCP_STG.CCP_MBRSHP_XREF)
SELECT DISTINCT CLAIM_HDR.ICN_NUM AS ICN_NUM,
CLAIM_HDR.SBCR_ID AS SBCR_ID,
CLAIM_HDR.MBR_ID AS MBR_ID,
CLAIM_HDR.MBR_FIRST_NAME AS MBR_FIRST_NAME,
CLAIM_HDR.MBR_MI AS MBR_MI,
CLAIM_HDR.MBR_LAST_NAME AS MBR_LAST_NAME,
CLAIM_HDR.MBR_BIRTH_DATE AS MBR_BIRTH_DATE,
CLAIM_HDR.GENDER_TYPE_CD AS GENDER_TYPE_CD,
CLAIM_HDR.SBCR_RLTNSHP_TYPE_CD AS SBCR_RLTNSHP_TYPE_CD,
CLAIM_HDR.SBCR_FIRST_NAME AS SBCR_FIRST_NAME,
CLAIM_HDR.SBCR_MI AS SBCR_MI,
CLAIM_HDR.SBCR_LAST_NAME AS SBCR_LAST_NAME,
CLAIM_HDR.SBCR_ADDR_LINE_1 AS SBCR_ADDR_LINE_1,
CLAIM_HDR.SBCR_ADDR_LINE2 AS SBCR_ADDR_LINE2,
CLAIM_HDR.SBCR_ADDR_CITY AS SBCR_ADDR_CITY,
CLAIM_HDR.SBCR_ADDR_STATE AS SBCR_ADDR_STATE,
CLAIM_HDR.SBCR_ZIP_CD AS SBCR_ZIP_CD,
CLAIM_HDR.PRVDR_NUM AS PRVDR_NUM,
CLAIM_HDR.CLM_PRCSSD_DT AS CLM_PRCSSD_DT,
CLAIM_HDR.CLM_TYPE_CLASS_CD AS CLM_TYPE_CLASS_CD,
CLAIM_HDR.AUTHO_NUM AS AUTHO_NUM,
CLAIM_HDR.TOT_BILLED_AMT AS TOT_BILLED_AMT,
CLAIM_HDR.HCFA_DRG_TYPE_CD AS HCFA_DRG_TYPE_CD,
CLAIM_HDR.FCLTY_ADMIT_DT AS FCLTY_ADMIT_DT,
CLAIM_HDR.ADMIT_TYPE AS ADMIT_TYPE,
CLAIM_HDR.DSCHRG_STATUS_CD AS DSCHRG_STATUS_CD,
CLAIM_HDR.FILE_BILLING_NPI AS FILE_BILLING_NPI,
CLAIM_HDR.CLAIM_LOCATION_CD AS CLAIM_LOCATION_CD,
CLAIM_HDR.CLM_RELATED_ICN_1 AS CLM_RELATED_ICN_1,
CLAIM_HDR.SUBSCR_INSGRP_NM,
CLAIM_HDR.CAC,
CLAIM_HDR.PRVDR_PTNT_ACC_ID,
CLAIM_HDR.BILL_TYPE,
CLAIM_DTL.FIRST_SRVC_DT AS FIRST_SRVC_DT,
CLAIM_DTL.LAST_SRVC_DT AS LAST_SRVC_DT,
CLAIM_DTL.PLC_OF_SRVC_CD AS PLC_OF_SRVC_CD,
PROV.PROV_LST_NM AS BILL_PROV_LST_NM,
PROV.PROV_FST_NM AS BILL_PROV_FST_NM,
PROV.PROV_MD_NM AS BILL_PROV_MID_NM,
PROV.PROV_BILL_ADR1 AS BILL_PROV_ADDR1,
PROV.PROV_BILL_CITY AS BILL_PROV_CITY,
PROV.PROV_BILL_STATE AS BILL_PROV_STATE,
PROV.PROV_BILL_ZIP AS BILL_PROV_ZIP,
PROV.PROV_SEC_ID AS BILL_PROV_EIN,
PROV.PROV_ID AS SERV_FAC_ID    ,
PROV.PROV_ADR1 AS SERV_FAC_ADDR1          ,
PROV.PROV_CITY AS SERV_FAC_CITY ,
PROV.PROV_STATE AS SERV_FAC_STATE          ,
PROV.PROV_ZIP AS     SERV_FAC_ZIP ,
CHK_PAYMNT.CLM_PMT_PAYEE_ADDR_LINE_1,
CHK_PAYMNT.CLM_PMT_PAYEE_ADDR_LINE_2,
CHK_PAYMNT.CLM_PMT_PAYEE_CITY,
CHK_PAYMNT.CLM_PMT_PAYEE_STATE_CD,
CHK_PAYMNT.CLM_PMT_PAYEE_POSTAL_CD,
CLAIM_HDR.CREAT_RUN_CYC_EXEC_SK
FROM CLAIM_DTL,(select * FROM CCP_STG.CLM_DETAIL_PRESTG WHERE ACT_CD <>'D') CLM_DETAIL_PRESTG, CLAIM_HDR,CCP_STG.MBR_XREF,PROV,CCP_STG.CLM_PAYMNT_CLMEXT_PRESTG CLM_PAYMNT,CCP_STG.CLM_PAYMNT_CHKEXT_PRESTG CHK_PAYMNT
WHERE
CLAIM_HDR.ICN_NUM = CLM_DETAIL_PRESTG.ICN_NUM
AND       CLAIM_HDR.ICN_NUM = CLAIM_DTL.ICN_NUM
AND CLAIM_HDR.ICN_NUM=CLM_PAYMNT.ICN_NUM(+)
AND CLM_PAYMNT.CLM_PMT_CHCK_ACCT=CHK_PAYMNT.CLM_PMT_CHCK_ACCT
AND CLM_PAYMNT.CLM_PMT_CHCK_NUM=CHK_PAYMNT.CLM_PMT_CHCK_NUM
AND CLAIM_HDR.MBR_ENROLL_ID = MBR_XREF.MBR_ENROLLL_ID
AND CLM_DETAIL_PRESTG.FIRST_SRVC_DT >= 20110101
AND MBR_XREF.NEW_MBR_FLG = 'Y'
AND PROV.PROV_ID(+)=SUBSTR(CLAIM_HDR.PRVDR_NUM,6)
AND MOD(SUBSTR(CLAIM_HDR.ICN_NUM,14,2),2)=0
UNION ALL
SELECT DISTINCT CLAIM_HDR.ICN_NUM AS ICN_NUM,
CLAIM_HDR.SBCR_ID AS SBCR_ID,
CLAIM_HDR.MBR_ID AS MBR_ID,
CLAIM_HDR.MBR_FIRST_NAME AS MBR_FIRST_NAME,
CLAIM_HDR.MBR_MI AS MBR_MI,
CLAIM_HDR.MBR_LAST_NAME AS MBR_LAST_NAME,
CLAIM_HDR.MBR_BIRTH_DATE AS MBR_BIRTH_DATE,
CLAIM_HDR.GENDER_TYPE_CD AS GENDER_TYPE_CD,
CLAIM_HDR.SBCR_RLTNSHP_TYPE_CD AS SBCR_RLTNSHP_TYPE_CD,
CLAIM_HDR.SBCR_FIRST_NAME AS SBCR_FIRST_NAME,
CLAIM_HDR.SBCR_MI AS SBCR_MI,
CLAIM_HDR.SBCR_LAST_NAME AS SBCR_LAST_NAME,
CLAIM_HDR.SBCR_ADDR_LINE_1 AS SBCR_ADDR_LINE_1,
CLAIM_HDR.SBCR_ADDR_LINE2 AS SBCR_ADDR_LINE2,
CLAIM_HDR.SBCR_ADDR_CITY AS SBCR_ADDR_CITY,
CLAIM_HDR.SBCR_ADDR_STATE AS SBCR_ADDR_STATE,
CLAIM_HDR.SBCR_ZIP_CD AS SBCR_ZIP_CD,
CLAIM_HDR.PRVDR_NUM AS PRVDR_NUM,
CLAIM_HDR.CLM_PRCSSD_DT AS CLM_PRCSSD_DT,
CLAIM_HDR.CLM_TYPE_CLASS_CD AS CLM_TYPE_CLASS_CD,
CLAIM_HDR.AUTHO_NUM AS AUTHO_NUM,
CLAIM_HDR.TOT_BILLED_AMT AS TOT_BILLED_AMT,
CLAIM_HDR.HCFA_DRG_TYPE_CD AS HCFA_DRG_TYPE_CD,
CLAIM_HDR.FCLTY_ADMIT_DT AS FCLTY_ADMIT_DT,
CLAIM_HDR.ADMIT_TYPE AS ADMIT_TYPE,
CLAIM_HDR.DSCHRG_STATUS_CD AS DSCHRG_STATUS_CD,
CLAIM_HDR.FILE_BILLING_NPI AS FILE_BILLING_NPI,
CLAIM_HDR.CLAIM_LOCATION_CD AS CLAIM_LOCATION_CD,
CLAIM_HDR.CLM_RELATED_ICN_1 AS CLM_RELATED_ICN_1,
CLAIM_HDR.SUBSCR_INSGRP_NM,
CLAIM_HDR.CAC,
CLAIM_HDR.PRVDR_PTNT_ACC_ID,
CLAIM_HDR.BILL_TYPE,
CLAIM_DTL.FIRST_SRVC_DT AS FIRST_SRVC_DT,
CLAIM_DTL.LAST_SRVC_DT AS LAST_SRVC_DT,
CLAIM_DTL.PLC_OF_SRVC_CD AS PLC_OF_SRVC_CD,
PROV.PROV_LST_NM AS BILL_PROV_LST_NM,
PROV.PROV_FST_NM AS BILL_PROV_FST_NM,
PROV.PROV_MD_NM AS BILL_PROV_MID_NM,
PROV.PROV_BILL_ADR1 AS BILL_PROV_ADDR1,
PROV.PROV_BILL_CITY AS BILL_PROV_CITY,
PROV.PROV_BILL_STATE AS BILL_PROV_STATE,
PROV.PROV_BILL_ZIP AS BILL_PROV_ZIP,
PROV.PROV_SEC_ID AS BILL_PROV_EIN,
PROV.PROV_ID AS SERV_FAC_ID    ,
PROV.PROV_ADR1 AS SERV_FAC_ADDR1          ,
PROV.PROV_CITY AS SERV_FAC_CITY ,
PROV.PROV_STATE AS SERV_FAC_STATE          ,
PROV.PROV_ZIP AS     SERV_FAC_ZIP ,
CHK_PAYMNT.CLM_PMT_PAYEE_ADDR_LINE_1,
CHK_PAYMNT.CLM_PMT_PAYEE_ADDR_LINE_2,
CHK_PAYMNT.CLM_PMT_PAYEE_CITY,
CHK_PAYMNT.CLM_PMT_PAYEE_STATE_CD,
CHK_PAYMNT.CLM_PMT_PAYEE_POSTAL_CD,
CLAIM_HDR.CREAT_RUN_CYC_EXEC_SK
FROM CLAIM_DTL, CLAIM_HDR,MBR_XREF,PROV,CCP_STG.CLM_PAYMNT_CLMEXT_PRESTG CLM_PAYMNT,CCP_STG.CLM_PAYMNT_CHKEXT_PRESTG CHK_PAYMNT
WHERE CLAIM_HDR.ICN_NUM = CLAIM_DTL.ICN_NUM
AND CLAIM_HDR.ICN_NUM=CLM_PAYMNT.ICN_NUM(+)
AND CLM_PAYMNT.CLM_PMT_CHCK_ACCT=CHK_PAYMNT.CLM_PMT_CHCK_ACCT
AND CLM_PAYMNT.CLM_PMT_CHCK_NUM=CHK_PAYMNT.CLM_PMT_CHCK_NUM
AND CLAIM_HDR.MBR_ENROLL_ID = MBR_XREF.MBR_ENROLLL_ID
-- AND TRUNC(CLAIM_HDR.PRESTG_INSRT_DT) = TRUNC(SYSDATE)
AND CLAIM_HDR.CREAT_RUN_CYC_EXEC_SK = 123638.000000000000000
AND MBR_XREF.NEW_MBR_FLG = 'N'
AND PROV.PROV_ID(+)=SUBSTR(CLAIM_HDR.PRVDR_NUM,6)
AND MOD(SUBSTR(CLAIM_HDR.ICN_NUM,14,2),2)=0;

CTAS, INSERT million of records

Hi All,
I have a table which has approx 20 million record, I will delete about 10 million record. After some research, I decided to perform CTAS + TRUNCATE rather than DELETE.
I will be executing the following statements, TEMP_TABLE will retain the record I wish to keep.
1. CREATE TEMP_TABLE AS ( SELECT * FROM ACTUAL_TABLE WHERE DATE BETWEEN X AND Y );
2. TRUNCATE TABLE ACTUAL_TABLE;
3. INSERT /*+ append */ INTO ACTUAL_TABLE (SELECT * FROM TEMP_TABLE);
4. DROP TABLE TEMP_TABLE;
My production database is running on Oracle 10g, I am worried the INSERT operation might fail due to the large amount of records to be transferred (Est. approx. 10 million records)
I have read by adding append hints might help during the insert process and UNDO tablespace might not be sufficient for huge record inserts.
How can I improve the process and avoid any possible failures?
Please kindly advise.
Thank you.

What do you mean by your INSERT will fail. Is your UNDO Tablespace not AUTO EXTENDABLE?
Another option is instead of doing the insert, you can
1. drop the ACTUAL_TABLE
2. Rename the TEMP_TABLE as ACTUAL_TABLE
3. Re Create the indexes, constraints, Triggers on the table back.
Edited by: Karthick_Arp on Apr 29, 2009 10:15 PM

Why does recording delay change?

so yesterday i recorded vox and acoustic gtr totally fine. then i went to add bass today and i get a huge recording lag in placement of recorded audio. what changed this? everythings been stable for months. do i really have to go through all this recording delay calculation trouble just to have it work right again? seems totally ridiculous.
cory

Did anything at all change between yesterday and today? Did you add any latency inducing plug-ins (or are you using any currently)?
As well, updating your profile, as far as equipment goes, might help zero in on your problem.
jord

First time an SQL expression is placed on report a DB SELECT executes

The same problem can be created using the normal Crystal Reports XI Release 2 developer environment and/or code (not only a code issue). I'm using CR XI.
Symptom:
We dynamically auto generate SQL Expressions, Tables, Joins, Formula's and anything through C# and place it onto the Crystal Report through code via run-time user input in a web environment. I recieved a notification from one of my DB admins that crystal reports is causing massive memory consumption via unknown SELECT statements that have no joins and/or WHERE criteria.
Some Detective Work/More Info:
After using Microsoft "SQL Profiler" along with Crystal, I understand what is happening but don't know the "work around" to make Crystal stop executing the following SELECT scenario.
Anytime I create a new "SQL Expression" for the first time and then physically "drag and drop" it onto the report then Crystal is executing a "silent" SELECT statement against the database in the design environment. I'm calling it "silent" because I need MS SQL Profiler to see it happen. I'm guessing that this is used for validation or something but this is causing problems when automatically generating a report in a production environment.
Steps to re-create:
1. Open MS "SQL Profiler" and get it running. (will show Crystal Engine silently executes the SELECTS)
2. Add a new "SQL Expression" to your report.
3. Drag and Drop your new "SQL Expression onto your report
4. You will see that Crystal has created an SQL query and executed it against your database in design environment.
The Problem:
I can see under normal circumstances why you might want this funtionality (if it's actually used for the Crystal Engine to validate your SQL Expression). But, What also makes this functionality horrible is that on my behalf Crystal is creating these SELECT statements and using cross joins which is a major problem in a production environment. As a result, huge record sets are being created on our DB Server. I don't believe that this has any purpose in a production evironment when the cross-joins can create huge amounts of results just for the sake of Crystal Internally validating a new SQL Expression placed onto a report. It would be nice to disable this functionality in production. I don't know a "work around" since these SELECT queries are created on my behalf by the Crystal Engine at design time (via code auto generation in production).
Questions:
Can this functionality be disabled to prevent a production server from incurring the execution of these queries?
Anybody else notice this and have a "work around"?

This is a cross post of:
1st time an SQL expression is placed on report a DB SELECT executes
Please do not cross post. See the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement].
The above post has been moved to the Crystal Reports Design forum, thus locking this thread.
Ludek

1st time an SQL expression is placed on report a DB SELECT executes

The same problem can be created using the normal Crystal Reports XI Release 2 developer environment and/or code (not only a code issue).
Symptom:
We dynamically auto generate SQL Expressions, Tables, Joins, Formula's and anything through C# and place it onto the Crystal Report through code via run-time user input in a web environment. I recieved a notification from one of my DB admins that crystal reports is causing massive memory consumption via unknown SELECT statements that have no joins and/or WHERE criteria.
Some Detective Work/More Info:
After using Microsoft "SQL Profiler" along with Crystal, I understand what is happening but don't know the "work around" to make Crystal stop executing the following SELECT scenario.
Anytime I create a new "SQL Expression" for the first time and then physically "drag and drop" it onto the report then Crystal is executing a "silent" SELECT statement against the database in the design environment. I'm calling it "silent" because I need MS SQL Profiler to see it happen. I'm guessing that this is used for validation or something but this is causing problems when automatically generating a report in a production environment.
Steps to re-create:
1. Open MS "SQL Profiler" and get it running. (will show Crystal Engine silently executes the SELECTS)
2. Add a new "SQL Expression" to your report.
3. Drag and Drop your new "SQL Expression onto your report
4. You will see that Crystal has created an SQL query and executed it against your database in design environment.
The Problem:
I can see under normal circumstances why you might want this funtionality (if it's actually used for the Crystal Engine to validate your SQL Expression). But, What also makes this functionality horrible is that on my behalf Crystal is creating these SELECT statements and using cross joins which is a major problem in a production environment. As a result, huge record sets are being created on our DB Server. I don't believe that this has any purpose in a production evironment when the cross-joins can create huge amounts of results just for the sake of Crystal Internally validating a new SQL Expression placed onto a report. It would be nice to disable this functionality in production. I don't know a "work around" since these SELECT queries are created on my behalf by the Crystal Engine at design time (via code auto generation in production).
Questions:
Can this functionality be disabled to prevent a production server from incurring the execution of these queries?
Anybody else notice this and have a "work around"?

Note that this is a "Lagacy Application Development SDKs" forum and as such it is dedicated to topics related to legacy SDKs, including the Report Designer Component (RDC), OCX, VCL, and Crystal Reports Print Engine (CRPE).
As your issue concerns the Crystal Report Designer (crw32.exe), transferring to the Crystal Reports Design forum:
SAP Crystal Reports
Ludek

First time an SQL expression is placed on report a DB SELECT executes -CRXI

The same problem can be created using the normal Crystal Reports XI Release 2 developer environment and/or code (not only a code issue).
Symptom:
We dynamically auto generate SQL Expressions, Tables, Joins, Formula's and anything through C# and place it onto the Crystal Report through code via run-time user input in a web environment. I recieved a notification from one of my DB admins that crystal reports is causing massive memory consumption via unknown SELECT statements that have no joins and/or WHERE criteria.
Some Detective Work/More Info:
After using Microsoft "SQL Profiler" along with Crystal, I understand what is happening but don't know the "work around" to make Crystal stop executing the following SELECT scenario.
Anytime I create a new "SQL Expression" for the first time and then physically "drag and drop" it onto the report then Crystal is executing a "silent" SELECT statement against the database in the design environment. I'm calling it "silent" because I need MS SQL Profiler to see it happen. I'm guessing that this is used for validation or something but this is causing problems when automatically generating a report in a production environment.
Steps to re-create:
1. Open MS "SQL Profiler" and get it running. (will show Crystal Engine silently executes the SELECTS)
2. Add a new "SQL Expression" to your report.
3. Drag and Drop your new "SQL Expression onto your report
4. You will see that Crystal has created an SQL query and executed it against your database in design environment.
The Problem:
I can see under normal circumstances why you might want this funtionality (if it's actually used for the Crystal Engine to validate your SQL Expression). But, What also makes this functionality horrible is that on my behalf Crystal is creating these SELECT statements and using cross joins which is a major problem in a production environment. As a result, huge record sets are being created on our DB Server. I don't believe that this has any purpose in a production evironment when the cross-joins can create huge amounts of results just for the sake of Crystal Internally validating a new SQL Expression placed onto a report. It would be nice to disable this functionality in production. I don't know a "work around" since these SELECT queries are created on my behalf by the Crystal Engine at design time (via code auto generation in production).
Questions:
Can this functionality be disabled to prevent a production server from incurring the execution of these queries?
Anybody else notice this and have a "work around"?

duplicate - please do not post multiple times

Huge Records

Similar Messages

Maybe you are looking for