Issue with loop in table control

Hello experts,
I have 20 entries in my table control but the loop is going through only for 10 entries..please help me?
Thanks

Hi
In PBO
module status_your_screen_number.
loop at itab with control tc.
endloop.
in PAI.
loop at itab.
module modify_itab
endloop.
in Program
Module status_your_screen_Number.
describe table itab lines tc-lines -
> THis will give you Scroll Bars for Table Control
endmodule
module modify_itab. -
> If Required ( If you are modifying the Data of table control )
DESCRIBE TABLE itab LINES lin.
IF tc-current_line > lin.
APPEND itab.
ELSE.
MODIFY itab INDEX tc-current_line. ---> This Ensures your data both Upward And Downward Scrolling
ENDIF.
endmodule
Cheers
Ram
Edited by: Ramchander Krishnamraju on Oct 28, 2009 8:59 AM
Edited by: Ramchander Krishnamraju on Oct 28, 2009 9:26 AM

Similar Messages

Issue with Update of Table VARINUM

Hi,
I am getting waiting Issues with Update of table VARINUM. Has anybody faced such an issue.
I have a lot of Jobs which are running in background. I am submitting it through a report. what can be the issue.
Regards,
Abhishek jolly

Thisi is quite old, but not answered properly yet, so there you go:
SAP generates a new job and temporary variant on report RSDBSPJS, for each HTTP call,which creates database locks on table VARINUM .
This causes any heavyweight BSP application to hang and give timeout errors.
The problem is fixed applying OSS note 1791958, which is not included in any service pack.

Issue with data dictionary -Table maintanance generator

Hi all,
I have an issue with Data dictionary, table maintenance generator. I have entered some records in a custom table (ZBCSECROLETOGRP) and changed the delivery class from C to A. When I create the table maintainance generator, I am encountered with the following errors:
1)Field ZBCSECROLETOGRP-PORTALGROUP shortened (new visible length: 000032)
2)0012 could not be generated
3)In TCTRL_ZBCSECROLETOGRP field LENGTH has the invalid value 01
My main motto is to create the table maintainace generator and transport to the furthur systems .
Please help.
ThnX in advance,
Vishal..

HI,
Regenerate the table maintenance by selecting the checkbox of "Modified field structure" => new entry & then save.
Also ensure that the new changes are not affecting old data bcz of data type changes. If that is the case, then delete the old records, regenerate table maint. & re-enter those records which you had deleted.
Thanks,
Best regards,
Prashant

CVC creation - Strange issue with Master data table of 9AMATNR

Hi Experts,
We have encountered a strange issue with Master data table (/BI0/9APMATNR) of info object 9AMATNR.
We have a BADI implemented for checking the valid Characteristic before creation of the CVC using transaction /SAPAPO/MC62. This BADI puts a select on master data tab of material /BI0/9APMATNR and returns no value. But the material actually exists in the table (checked through SE16).
Now we go inside the info object 9AMATNR and go to the Master data Tab. There we go inside the master table
/BI0/9APMATNR and activate that. After activating the table it is read by the select statement inside BADI (Strange) and allows the CVC to be created.
Ideally it should not allow us to activate the SAP standard table /BI0/9APMATNR. I observed that in technical settings of this table it has single record buffering as switched on. (But as per my knowledge buffer gets refreshed every 2 to 4 mins and not in 2 days or something).
Your expert comment is valuable to us. Thanks.
Best Regards,
Chandan Dubey

Hi Chandan,
Try to use a WAIT statment with 5 seconds before your select statment.
I'm not sure whether this will work. Anyway check it and let me know the result.
Regards,
Siva.

Performance issue with Loop under Loop

Hi,
I have an issue with the performance, as per the requirement I have to use the Loop under Loop logic.
I have sorted the Where condition field in Parent Loop and also in Child Loop like below :
SELECT GUID_PRCTSC   "Primary Key as GUID in "RAW" Format
         GUID_PR       "Primary Key as GUID in "RAW" Format
         STCTS         "Numbering Scheme for Customs Tariff System
         DATAB         "Definitive Date (Valid-From Time)
         GUID_CTSNUMC "Primary Key as GUID in "RAW" Format
         FROM /SAPSLL/PRCTSC
         INTO TABLE T_PRCTSC
         WHERE STCTS IN S_STCTS.
IF T_PRCTSC IS INITIAL.
    MESSAGE : I007(ZMSSG) WITH 'Data not available for this entry'.
    STOP.
ENDIF.
SORT T_PRCTSC BY GUID_PR.
SELECT GUID_PRGEN "Primary Key as GUID in "RAW" Format "+ DG1K902277
         GUID_PR     "Primary Key as GUID in "RAW" Format
         ATTR05A     "Materail Type
         ATTR05B     "Sub-Family
         ATTR05C     "SPEC BUS + DG1K902190
         ATTR10A     "Materail Group
         ATTR20A     "SUBSTANCE ID
         FROM /SAPSLL/PRGEN
         INTO TABLE T_PRGEN
         FOR ALL ENTRIES IN T_TCOATV20
         WHERE ATTR20A EQ T_TCOATV20-ATTRV20
           AND ATTR05A IN S_ATR5A " +DG1K902168
           AND ATTR05C IN S_ATR5C. " + DG1K902190
IF T_PRGEN IS INITIAL.
    MESSAGE : I007(ZMSSG) WITH 'Data not available for this entry'.
    STOP.
ENDIF.
*N-23
SORT T_PRGEN BY GUID_PR.
There are 90,000 records available in the table T_PRGEN.
LOOP AT T_PRGEN INTO WA_PRGEN.
    IF SY-SUBRC = 0.
       WA_FINAL-ATTR05A       = WA_PRGEN-ATTR05A.
       WA_FINAL-ATTR05B       = WA_PRGEN-ATTR05B.
       WA_FINAL-ATTR05C       = WA_PRGEN-ATTR05C. " + DG1K902190
       WA_FINAL-ATTR10A       = WA_PRGEN-ATTR10A.
       WA_FINAL-ATTR20A       = WA_PRGEN-ATTR20A.
    ENDIF.
    READ TABLE T_V_TCAV201 INTO WA_V_TCAV201 WITH KEY ATTRV20 = WA_PRGEN-ATTR20A.
    IF SY-SUBRC = 0.
      WA_FINAL-TEXT1   = WA_V_TCAV201-TEXT1.    "SUBID-TEXT1
    ENDIF.
    READ TABLE T_PNTPR INTO WA_PNTPR WITH KEY GUID_PR = WA_PRGEN-GUID_PR.
    IF SY-SUBRC = 0.
       WA_FINAL-PRVSY = WA_PNTPR-PRVSY.   "PROD NO
       WA_FINAL-GRVSY = WA_PNTPR-GRVSY.   "LOGICAL SYS GROUP
    ENDIF.
* TO Remove the Leading Zeros from prvsy
    SHIFT WA_FINAL-PRVSY LEFT DELETING LEADING '0'.
    READ TABLE T_CORSTA INTO WA_CORSTA WITH KEY GUID_MOBJ = WA_PNTPR-GUID_PR.
    IF SY-SUBRC = 0.
      WA_FINAL-QUAL_STA = WA_CORSTA-QUAL_STA.
    ENDIF.
    READ TABLE T_PR INTO WA_PR WITH KEY GUID_PR = WA_PNTPR-GUID_PR.
*& IN THE PROD MASTER PRODUCT CHANGED ON VALUE HAS BEEN   &
*& MAINTAINED AS SINGLE '0', THIS WILL CAUSE ISSUES WHILE &
*& USING CONVERSION EXIT TO DISPLAY THE DATE FORMAT IN   &
*& MM/DD/YYYY HH:MM:SEC                                  &
    IF SY-SUBRC = 0.
      IF WA_PR-CHTSP = '0'.
        WA_FINAL-CRTSP   = WA_PR-CRTSP.
        wa_final-chtsp   = W_DATE.
      ENDIF.
      IF WA_PR-CHTSP NE '0'.
        WA_FINAL-CRTSP   = WA_PR-CRTSP.
        wa_final-chtsp   = WA_PR-CHTSP.
      ENDIF.
    ENDIF.
    READ TABLE T_PRT INTO WA_PRT WITH KEY GUID_PR = WA_PR-GUID_PR.
    IF SY-SUBRC = 0.
      WA_FINAL-PRTXT   = WA_PRT-PRTXT.
    ENDIF.
LOOP AT T_PRCTSC INTO WA_PRCTSC WHERE GUID_PR = WA_PRGEN-GUID_PR. "+DG1K902258 - Performance issue
        IF SY-SUBRC = 0.
*& TO FILL ATTR20A,PRVSY FOR DIFF STCTS AND CCNGN FOR     |
*& EACH LOOP                                             |
          IF WA_FINAL-ATTR20A IS INITIAL
          AND WA_FINAL-PRVSY IS INITIAL.
            IF WA_PRGEN-GUID_PR = WA_PNTPR-GUID_PR. "This condition is to fill up all the rows for the same
                                                    " Subid which have multiple stcts fields.
           IF SY-SUBRC = 0.
              WA_FINAL-ATTR05A       = WA_PRGEN-ATTR05A.
              WA_FINAL-ATTR05B       = WA_PRGEN-ATTR05B.
              WA_FINAL-ATTR05C       = WA_PRGEN-ATTR05C. " + DG1K902190
              WA_FINAL-ATTR10A       = WA_PRGEN-ATTR10A.
              WA_FINAL-ATTR20A       = WA_PRGEN-ATTR20A.
             ENDIF.
              IF SY-SUBRC = 0.
                WA_FINAL-TEXT1   = WA_V_TCAV201-TEXT1.    "SUBID-TEXT1
              ENDIF.
              IF SY-SUBRC = 0.
                WA_FINAL-PRVSY = WA_PNTPR-PRVSY.   "PROD NO
                WA_FINAL-GRVSY = WA_PNTPR-GRVSY.   "LOGICAL SYS GROUP
              ENDIF.
* TO Remove the Leading Zeros from prvsy
              SHIFT WA_FINAL-PRVSY LEFT DELETING LEADING '0'.
              IF SY-SUBRC = 0.
                WA_FINAL-QUAL_STA = WA_CORSTA-QUAL_STA.
              ENDIF.
              IF SY-SUBRC = 0.
                IF WA_PR-CHTSP = '0'.
                  WA_FINAL-CRTSP   = WA_PR-CRTSP.
                  WA_final-chtsp   = W_DATE.
                ENDIF.
                IF WA_PR-CHTSP NE '0'.
                  WA_FINAL-CRTSP   = WA_PR-CRTSP.
                  WA_final-chtsp   = WA_PR-CHTSP.
                ENDIF.
              ENDIF.
              IF SY-SUBRC = 0.
                WA_FINAL-PRTXT   = WA_PRT-PRTXT.
              ENDIF.
            ENDIF.
          ENDIF.
      IF SY-SUBRC = 0. " + DG1K902198
            WA_FINAL-GUID_PR      = WA_PRCTSC-GUID_PR.
            WA_FINAL-STCTS        = WA_PRCTSC-STCTS.
            WA_FINAL-DATAB        = WA_PRCTSC-DATAB.       " + DG1K902198
          ENDIF.
         READ TABLE T_CTSNUMC INTO WA_CTSNUMC WITH KEY GUID_CTSNUMC = WA_PRCTSC-GUID_CTSNUMC.
          IF SY-SUBRC = 0.
            WA_FINAL-CCNGN        = WA_CTSNUMC-CCNGN.
          ENDIF.
          APPEND WA_FINAL TO T_FINAL.
          CLEAR WA_FINAL.
        ENDIF.
    ENDLOOP.
    APPEND WA_FINAL TO T_FINAL.
    CLEAR WA_FINAL.
ENDLOOP.
Any suggestions to improve the performance will be appreciated!
Thanks & Regards,
Kittu
Edited by: Kittu on Mar 23, 2009 4:03 PM

Hi
Instead of using the LOOP under LOOP directly. use the read statement for second loop and from that index u start the loop.
eg:
LOOP AT ITAB1.
read table itab2 with key field1 = itab1 - field1.
if sy-subrc = 0.
loop at itab2 index sy-tabix.
if itab2-field1 = itab1 - field1.
< do u r operations >
else.
exit.
endif.
ENDLOOP.
this will increase the performance

Oracle 10g - issue with "DELETE from TABLE WHERE ID in (1,2,3)" (cfqueryparam used)

Hello, everyone.
I am having issues with running a DELETE statement on an Oracle 10g database.
DELETE
FROM tableA
WHERE ID in (1,2,3)
If there is only one ID for the IN clause, it works. But if more than one ID is supplied, I get an "SQL command not properly ended" error message. Here is the query as CF:
DELETE
FROM TRAINING
WHERE userID = <cfqueryparam cfsqltype="CF_SQL_VARCHAR" value="#trim(form.userID)#">
AND TRAINING_ID in <cfqueryparam value="#form.trainingIDs#" cfsqltype="CF_SQL_INTEGER" list="yes">
Anyone work with Oracle that can help me with this? I'm an experienced MS-SQL developer; Oracle is new to me.
Thanks,
^_^

Nevermind.. a co-worker just told me that I still have to use parenthesis around the values for the IN clause.

Issue with updating partitioned table

Hi,
Anyone seen this bug with updating partitioned tables.
Its very esoteric - its occurs when we update a partitioned table using a join to a temp table (not non-temp table) when the join has multiple joins and you're updating the partitoned column that isn't the first column in the primary key and the table contains a bit field. We've tried changing just one of these features and the bug disappears.
We've tested this on 15.5 and 15.7 SP122 and the error occurs in both of them.
Here's the test case - it does the same operation of a partitioned table and a non-partitioned table, but the partitioned table shows and error of "Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'".
I'd be interested if anyone has seen this and has a version of Sybase without the issue.
Unfortunately when it happens on a replicated table - it takes down rep server.
CREATE TABLE #table1
    (   PK          char(8) null,
        FileDate        date,
        changed         bit
CREATE TABLE partitioned (
PK         char(8) NOT NULL,
ValidFrom     date DEFAULT current_date() NOT NULL,
ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
LOCK DATAROWS
PARTITION BY RANGE (ValidTo)
( p2014 VALUES <= ('20141231') ON [default],
p2015 VALUES <= ('20151231') ON [default],
pMAX VALUES <= (MAX) ON [default]
CREATE UNIQUE CLUSTERED INDEX pk
ON partitioned(PK, ValidFrom, ValidTo)
LOCAL INDEX
CREATE TABLE unpartitioned (
PK         char(8) NOT NULL,
ValidFrom     date DEFAULT current_date() NOT NULL,
ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
LOCK DATAROWS
CREATE UNIQUE CLUSTERED INDEX pk
ON unpartitioned(PK, ValidFrom, ValidTo)
insert partitioned
select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
insert unpartitioned
select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
insert #table1
select "ET00jPzh", "Jan 15 2015", 1
union all
select "ET00jPzh", "Jan 15 2015", 1
go
update partitioned
set    ValidTo = dateadd(dd,-1,FileDate)
from   #table1 t
inner join partitioned p on (p.PK = t.PK)
where p.ValidTo = '99991231'
and    t.changed = 1
go
update unpartitioned
set    ValidTo = dateadd(dd,-1,FileDate)
from   #table1 t
inner join unpartitioned u on (u.PK = t.PK)
where u.ValidTo = '99991231'
and    t.changed = 1
go
drop table #table1
go
drop table partitioned
drop table unpartitioned
go

wrt to replication - it is a bit unclear as not enough information has been stated to point out what happened. I also am not sure that your DBA's are accurately telling you what happened - and may have made the problem worse by not knowing themselves what to do - e.g. 'losing' the log points to fact that someone doesn't know what they should.   You can *always* disable the replication secondary truncation point and resync a standby system, so claims about 'losing' the log are a bit strange to be making.
wrt to ASE versions, I suspect if there are any differences, it may have to do with endian-ness and not the version of ASE itself.   There may be other factors.....but I would suggest the best thing would be to open a separate message/case on it.
Adaptive Server Enterprise/15.7/EBF 23010 SMP SP130 /P/X64/Windows Server/ase157sp13x/3819/64-bit/OPT/Fri Aug 22 22:28:21 2014:
-- testing with tinyint
1> use demo_db
1>
2> CREATE TABLE #table1
3>     (   PK          char(8) null,
4>         FileDate        date,
5> --        changed         bit
6> changed tinyint
7>     )
8>
9> CREATE TABLE partitioned (
10>   PK         char(8) NOT NULL,
11>   ValidFrom     date DEFAULT current_date() NOT NULL,
12>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
13>   )
14>
15> LOCK DATAROWS
16>   PARTITION BY RANGE (ValidTo)
17>   ( p2014 VALUES <= ('20141231') ON [default],
18>   p2015 VALUES <= ('20151231') ON [default],
19>   pMAX VALUES <= (MAX) ON [default]
20>         )
21>
22> CREATE UNIQUE CLUSTERED INDEX pk
23>   ON partitioned(PK, ValidFrom, ValidTo)
24>   LOCAL INDEX
25>
26> CREATE TABLE unpartitioned (
27>   PK         char(8) NOT NULL,
28>   ValidFrom     date DEFAULT current_date() NOT NULL,
29>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
30>   )
31> LOCK DATAROWS
32>
33> CREATE UNIQUE CLUSTERED INDEX pk
34>   ON unpartitioned(PK, ValidFrom, ValidTo)
35>
36> insert partitioned
37> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
38>
39> insert unpartitioned
40> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
41>
42> insert #table1
43> select "ET00jPzh", "Jan 15 2015", 1
44> union all
45> select "ET00jPzh", "Jan 15 2015", 1
(1 row affected)
(1 row affected)
(2 rows affected)
1>
2> update partitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join partitioned p on (p.PK = t.PK)
6> where p.ValidTo = '99991231'
7> and    t.changed = 1
Msg 2601, Level 14, State 6:
Server 'PHILLY_ASE', Line 2:
Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'
Command has been aborted.
(0 rows affected)
1>
2> update unpartitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join unpartitioned u on (u.PK = t.PK)
6> where u.ValidTo = '99991231'
7> and    t.changed = 1
(1 row affected)
1>
2> drop table #table1
1>
2> drop table partitioned
3> drop table unpartitioned
-- duplicating with 'int'
1> use demo_db
1>
2> CREATE TABLE #table1
3>     (   PK          char(8) null,
4>         FileDate        date,
5> --        changed         bit
6> changed int
7>     )
8>
9> CREATE TABLE partitioned (
10>   PK         char(8) NOT NULL,
11>   ValidFrom     date DEFAULT current_date() NOT NULL,
12>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
13>   )
14>
15> LOCK DATAROWS
16>   PARTITION BY RANGE (ValidTo)
17>   ( p2014 VALUES <= ('20141231') ON [default],
18>   p2015 VALUES <= ('20151231') ON [default],
19>   pMAX VALUES <= (MAX) ON [default]
20>         )
21>
22> CREATE UNIQUE CLUSTERED INDEX pk
23>   ON partitioned(PK, ValidFrom, ValidTo)
24>   LOCAL INDEX
25>
26> CREATE TABLE unpartitioned (
27>   PK         char(8) NOT NULL,
28>   ValidFrom     date DEFAULT current_date() NOT NULL,
29>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
30>   )
31> LOCK DATAROWS
32>
33> CREATE UNIQUE CLUSTERED INDEX pk
34>   ON unpartitioned(PK, ValidFrom, ValidTo)
35>
36> insert partitioned
37> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
38>
39> insert unpartitioned
40> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
41>
42> insert #table1
43> select "ET00jPzh", "Jan 15 2015", 1
44> union all
45> select "ET00jPzh", "Jan 15 2015", 1
(1 row affected)
(1 row affected)
(2 rows affected)
1>
2> update partitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join partitioned p on (p.PK = t.PK)
6> where p.ValidTo = '99991231'
7> and    t.changed = 1
Msg 2601, Level 14, State 6:
Server 'PHILLY_ASE', Line 2:
Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'
Command has been aborted.
(0 rows affected)
1>
2> update unpartitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join unpartitioned u on (u.PK = t.PK)
6> where u.ValidTo = '99991231'
7> and    t.changed = 1
(1 row affected)
1>
2> drop table #table1
1>
2> drop table partitioned
3> drop table unpartitioned

Issue with Data Load Table

Hi All,
       i am facing issue with apex 4.2.4 ,using the Data Load Table concept's and in this look up used the
      Where Clause option ,it seems to be not working this where clause ,Please help me on this

hi all,
    it looks this where clause not filter with 'N' data ,Please help me ,how to solve this or help me on this

Scalability issue with global temporary table.

Hi All,
Does create global temporary table would lock data disctionary like create table? if yes would not it be a scalable issue with multi user environment?
Thanks and Regards,
Rudra

Billy Verreynne wrote:
acadet wrote:
am I correct in interpreting your response that we should be using GTT's in favour of bulk operations and collections and in memory operations? No. I said collections cannot scale. This means due to the fact that collections reside in expensive PGA memory, you cannot stuff large data volumes into them. Thus they do not make an ideal storage bin for temporary data (e.g. data loaded from file or a web service). GTTs otoh do not suffer from the same restrictions, can be indexed and offer vastly better scalability and so on.
Multiple passes are often needed using such a data structure. Or filtering to find specific data. As a GTT is a SQL native, it offers a lot more flexibility and performance in this regard.
And this makes sense - as where do we put out persistent data? Also in tables, but ones of a persistent and not temporary kind like a GTT.
Collections are pretty useful - but limited in size and capability.
Rudra states:
I want to pull out few metrices from differnt tables and processing itIf this can't be achieved in a SQL statement, unless Rudra is a master of understatement then I would see GTT's as a waste of IO and programming effort. I agree.
My comments however were about choices for a temporary data storage bin in PL/SQL.I agree with your general comments regarding temporary storage bins in Oracle, but to say that collections don't scale is putting to narrow a definition on scaling. True, collections can be resource intensive in terms of memory and CPU requirements, but their persistence will generally be much shorter than other types of temporary storage. Given the right characteristics, collections will scale and given the wrong characteristics GTT's wont scale.
As you say it is all about choice. Getting back to the theme of this thread though, the original poster should be made aware that well designed and well coded applications are most likely to scale. Creating tables on the fly is generally considered bad practice and letting the database do what it does best, join tables in queries at the SQL level is considered good practice. The rest lies somewhere in between and knowing when to do which is why we get paid the big bucks (not). ;-)
Regards
Andre

Export Issues with Compressed Partition Tables?

We recently partitioned and compressed some large tables. It appears, but I'm not sure yet, that this is causing the export to run extremely slow. The database is at 10.2.0.2 and we are using the exp utility, not datapump. Does anyone know of any known issues with using exp to export compressed, partitioned tables?

can you give more details of the table structure with dbms_metadata if possible, and how you are taking the export please?
did you try to take an sql*trace of the export process to see what is going on behind, this is an introduction if you may need;
http://tonguc.wordpress.com/2006/12/30/introduction-to-oracle-trace-utulity-and-understanding-the-fundamental-performance-equation/

Issue with Tascam FW-1082 Control Surface

Anyone having issues with this connected to a mac Pro? I have one and upon turning on the unit, crashes the entire computer. If I boot with the unit connected, it'll sometimes keep OSX from doing a full boot, or if it does boot, FCP will hang on startup.
Spoke with tech support. Was only able to get it to work after disabling all network protocols, strange, but it did work. There's gotta be a better way to get this to work. Works fine on an i-mac.

Alas, the Tascam FW-1082 is never going to work with Snow Leopard because Tascam/Teac have discontinued support for it. I'd already been disappointed at reading the addendum on this page:
http://www.tascam.com/article;34,2034,3800.html
And I got the following mail reply to my inquiry to Tascam (downgrading to Leopard I would do, but I will not downgrade my Mac Pro from 12GB RAM to 4GB!):
Dear Mrs Noort,
Due to a general incompatibility with Apple's new 64-bit Audio Core engine, which cannot be resolved through an updated driver, we have decided to stop further driver development for the FW-1082.
If Final Cut Studio 3 runs on Leopard (OS 10.5..), there should be no problems in conjunction with this program.
The driver v.1.60 will work under Leopard up to a max. system RAM of 4 GB.
Best Regards,
V.Asmanidis, TASCAM Support

Issue with the shawdow table

I am in the process of understanding the shawdow table and the error log table.
i have a table created with a shadow table in place.
1. ex : table emp( empno, ename), emp_err( ...., empno,ename)
it contains the values (1,'A').
Now i place the empno with a data rule, unique not null ... and configure the operator
as MOVE TO ERROR.
when i try to insert a row with 1,A, its not only moving the new row to be inserted but also the existing row in the table emp ie two rows are getting populated in the error table emp_err
2. I have a scenario where i want to update a row in the fact, from an incoming row.
If there is no match of the incoming row to that of the fact, how do i put that into the
error_table ?
Any ideas or tricks appreciated.
Thanks
Narayana.

Hi,
Remove the the internal tables memory by using FREE statement after processing the internal table.
Also u can ask your Basis person to increase the page area.
Reward if helpful.
Regards,
Umasankar.

Issue with clearing internal table

Hi Gurus,
I am working on an issue, where when we run a std. report we see social number of the employee on the output screen, when I debugged the program I found that there are 2 internal tables where we are putting this SSN. I tried to clear the SSN at the both the places like:
loop at it_table.
clear it_table-SSN.
Endloop.
but still when I ran the report I am seeing social there. so can you please give me any idea of what I am doing wrong?
Thanks,
Rajeev Gupta

Hi rajeev,
even after ur clearing if the field is still populating it means again its filling the particular field in the later place.
1) keep ur code and while debuging just click on watchpoint and give ur field name go with f8 it will take u to the place the field is filling..
2) below that place clear that field and modify the table..

Row locking issue with version enabled tables

I've been testing the effect of locking in version enabled tables in order to assess workspace manager restrictions when updating records in different workspaces and I have encountered a locking problem where I can't seem to update different records of the same table in different sessions if these same records have been previously updated & committed in another workspace.
I'm running the tests on 11.2.0.3. I have ROW_LEVEL_LOCKING set to ON.
Here's a simple test case (I have many other test cases which fail as well but understanding why this one causes a locking problem will help me understand the results from my other test cases):
--Change tablespace names as required
create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
exec dbms_wm.gotoworkspace('LIVE');
insert into t1 values ('1', 'name1');
insert into t1 values ('2', 'name2');
insert into t1 values ('3', 'name3');
commit;
exec dbms_wm.enableversioning('t1');
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM1');
exec dbms_wm.gotoworkspace('TESTWSM1');
--update 2 records in a non-LIVE workspace in preparation for updating in different workspaces later
update t1 set name = name||'changed' where id in ('1', '2');
commit;
quit;
--Now in a separate session (called session 1 for this example) run the following without committing the changes:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--Now in another session (session 2) update a different record from the same table. The below update will hang waiting on the transaction in session 1 to complete (via commit/rollback):
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
I'm surprised records of different ids can't be updated in different sessions i.e. why does session 1 lock the update of record 2 which is not being updated anywhere else. I've tried this using different non-LIVE workspaces with similar results. I've tried changing table properties e.g. initrans with and still get a lock. The changes to table properties are successfully propagated to the _LT tables but not all the related workspace manager tables created for table T1 above. I'm not sure if this is the issue.
Note an example of the background workspace manager query that may create the lock is something like:
UPDATE TESTWSM.T1_LT SET LTLOCK = WMSYS.LT_CTX_PKG.CHECKNGETLOCK(:B6 , LTLOCK, NEXTVER, :B3 , 0,'UPDATE', VERSION, DELSTATUS, :B5 ), NEXTVER = WMSYS.LT_CTX_PKG.GETNEXTVER(NEXTVER,:B4 ,VERSION,:B3 ,:B2 ,683) WHERE ROWID = :B1
Any help with this will be appreciated. Thanks in advance.

Hi Ben,
Thanks for your quick response.
I've tested your suggestion and it does work with 2 workspaces but the same problem is enountered when additional workspaces are created.
It seems if multiple workspaces are used in a multi user environment, locks will be inevitable which will degrade performance especially if a long transaction is used.
Deadlocks can also be encountered where eventually one of the sessions is rolled back by the database.
Is there a way of avoiding this e.g. by controlling the creation of workspaces and table updates?
I've updated my test case below to demonstrate the extra workspace locking issue.
--change tablespace name as required
create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
exec dbms_wm.gotoworkspace('LIVE');
insert into t1 values ('1', 'name1');
insert into t1 values ('2', 'name2');
insert into t1 values ('3', 'name3');
commit;
exec dbms_wm.enableversioning('t1');
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM1');
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = name||'changed' where id in ('1', '2');
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
--end of original test case, start of additional workspace locking issue:
Session 1:
rollback;
Session 2:
rollback;
--update record in both workspaces
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM2');
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = name||'changed2' where id in ('1', '2');
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this now gets locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--update record 3 in TESTWSM2
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating LIVE
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating TESTWSM1 workspace too - so all have been updated since TESTWSM2 was created
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating every workspace afresh
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changedA' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changedB' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = 'changedC' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;

Issue with ADF Tree Table

Hi,
I have the following requirement where i need to display a tree table. Here is how the initial implementation is:
I have created the read only view for : ManagersVO > PoolsVO > MachinesVO. Where 'MachinesVO' is the destination view. And created view links between ManagersVO & PoolsVO using ManagerId and PoolsVO & MachinesVO using PoolId.
And using this implementation, successfully created tree table on the UI. Now we got an enhancement for this:
i.e., MachinesVO should return list of machines as per user logs in. i.e., we have 4 different roles. 'Super Admin', 'Sys Admin', 'App Admin', 'End User'. The default query for MachinesVO is for 'Super Admin'. The query for other user roles is different except the SELECT statement.
The requirement is to dynamically change the query of MachinesVO based on user logs in and display the tree table accordingly. To implement the same i have tried using setQuery() operation on 'MachinesVO' which results with the following error:
JBO-26016: InvalidOperException
Cause: You cannot set customer query (calling setQuery()) on a view object if it is the detail view object in a master detail view link.
Action: Do not call setQuery() if the view object is a detail.
Can one suggest me a best solution to implement this.
Thanks & Regards,
Kiran

Hi Navaneetha Krishnan,
Here is how i implemented based on your comments. As i have tree table based 3 different VO's, created the following method at middle view(i.e., PoolsVO).
1.Tree Model hierarchy
ManagersVO > PoolsVO > MachinesVO
I actually want to filter the data at Machines level. Hence wrote a method at PoolsVOImpls and exposed it in the PoolsVO client interface. Here is the code that i have placed in the PoolVOImpl
public class PoolsVOImpl extends ViewObjectImpl implements PoolsVO{
     * This is the default constructor (do not remove).
    public PoolsVOImpl () {
public void filterMachinesDataByUserRole(String userRole,String vzId){
    Row row = getCurrentRow();
    String query = "";
    if(row != null){
      RowSet rowSet = (RowSet)row.getAttribute("MachinesVO");
      if(rowSet != null){
        MachinesVOImpl machinesVOImpl = (MachinesVOImpl)rowSet.getViewObject();
        if(userRole.equalsIgnoreCase("SYS ADMIN")){
                machinesVOImpl .setWhereClause(query related to sysadmin);
         //Similarly for other user roles.
         executeQuery();
}And this piece of code needs to be executed before the jsff(which has the tree table) renders. Hence, i created a this methodAction as a default activity in the respective taskflow where the jsff is placed. Once this method get executed, the page should render the machines specific to the user.
Here is the issue: getCurrentRow() method call is returning always NULL.
Please correct me if i'm doing something wrong. I do tried the above mentioned approach by creating the method at '*ManagersVOImpl*' level too. Still the same issue.
Thanks & Regards,
Kiran

Issue with loop in table control

Similar Messages

Maybe you are looking for