Showing posts with label LD Error. Show all posts
Showing posts with label LD Error. Show all posts
Wednesday, January 27, 2016
LD Error building key for index
Error building key for index "c:\users\suprim~1.moh\appdata\local\temp\00004ftl001q.cdx" tag "Clrisk".
cursor_sharing should be exact
cursor_sharing should be exact
Friday, January 22, 2016
LD Login Error Table Definitions have undergone a change
select table_name from dba_tables where owner='LDBO' and temporary = 'Y' and table_name='TBLTEMPOPERATIONSTATISTICS';
DRop TABLE "LDBO"."TBLTEMPOPERATIONSTATISTICS" ;
CREATE GLOBAL TEMPORARY TABLE "LDBO"."TBLTEMPOPERATIONSTATISTICS"
( "NOPERCODE" NUMBER(3,0),
"NSUBCODE" NUMBER(3,0),
"COPERATIONNAME" VARCHAR2(100 BYTE),
"CSTARTTIME" DATE,
"CENDTIME" DATE,
"NTOTALROWS" NUMBER(12,0),
"NINITIALROWS" NUMBER(12,0),
"NFETCHROWS" NUMBER(12,0)
) ON COMMIT PRESERVE ROWS ;
ORA-06502 PLSQL numeric or value error character to number conversion error ORA-06512 at LDBO.SP_SERSEQ
SELECT voucher FROM LEDGER WHERE FIRMNUMBER='APXC-00001' and voucher like '%JV%' and Regexp_Like((SUBSTR(VOUCHER,-7,7)), '[[:alpha:]]');
SELECT MAX(SUBSTR(VOUCHER,-7,7)) FROM LEDGER WHERE FIRMNUMBER='APXC-00001' and voucher like '%JV%' and Regexp_Like((SUBSTR(VOUCHER,-7,7)), '[[:alpha:]]');
result should be numeric
SELECT MAX(SUBSTR(VOUCHER,-7,7)) FROM LEDGER WHERE FIRMNUMBER='APXC-00001' and voucher like '%JV%' and Regexp_Like((SUBSTR(VOUCHER,-7,7)), '[[:alpha:]]');
result should be numeric
ora-14450 ora-14452 global temporary table attempt to access a transactional temp table already in use
SELECT
distinct
ss.program "SOFTWARE",
SS.TERMINAL,
ss.username "USER",
'alter system disconnect session ''' || ss.sid || ',' || ss.serial# || ',@' || ss.inst_id || ''' immediate;'
fROM gv$process pr, gv$session ss, gv$sqlarea sqa,
(select sid
from gv$lock
where id1 = (
select object_id
from dba_objects
where owner = 'LDBO'
and object_name = 'TBLTEMPTRADESTATUS'))tbllock
WHERE pr.addr = ss.paddr
AND ss.username is not null
AND ss.sql_address = sqa.address(+)
AND ss.sql_hash_value = sqa.hash_value(+)
and ss.inst_id=pr.inst_id
and ss.sid = tbllock.sid
;
distinct
ss.program "SOFTWARE",
SS.TERMINAL,
ss.username "USER",
'alter system disconnect session ''' || ss.sid || ',' || ss.serial# || ',@' || ss.inst_id || ''' immediate;'
fROM gv$process pr, gv$session ss, gv$sqlarea sqa,
(select sid
from gv$lock
where id1 = (
select object_id
from dba_objects
where owner = 'LDBO'
and object_name = 'TBLTEMPTRADESTATUS'))tbllock
WHERE pr.addr = ss.paddr
AND ss.username is not null
AND ss.sql_address = sqa.address(+)
AND ss.sql_hash_value = sqa.hash_value(+)
and ss.inst_id=pr.inst_id
and ss.sid = tbllock.sid
;
Error while trying to retrieve text for error ORA-01019
Error while trying to retrieve text for error ORA-01019
VFP connection issue
check oracle path in Env Var
remove 11g path keep 10g path in starting
VFP connection issue
check oracle path in Env Var
remove 11g path keep 10g path in starting
Saturday, July 27, 2013
Windows 7 64 bit (unable to make connect to sql data source error# -1)
Error in odbc.dbf : Connectivity error: [Microsoft][ODBC driver for Oracle][Oracle]ORA-12541: TNS:no listener
Solution:
I have changed scb1213srv with scb1213 or someother name in directy.dbf, odbcad32, tnsnames.ora Now it is working
Cause:
Client IT team create ODBC using registry batch file, may scb1213srv is present some where.
ODBC is not points to listener address properly
Steps
Check your PATH and ORACLE_HOME environment variables
They should point to the location you installed the client and under which your tnsnames.ora file is located.
Solution:
I have changed scb1213srv with scb1213 or someother name in directy.dbf, odbcad32, tnsnames.ora Now it is working
Cause:
Client IT team create ODBC using registry batch file, may scb1213srv is present some where.
ODBC is not points to listener address properly
Steps
Check your PATH and ORACLE_HOME environment variables
They should point to the location you installed the client and under which your tnsnames.ora file is located.
LD error money obligation cexist ORA-01422 exact fetch returns more than one requested number of rows
That error occurs in a SELECT ... INTO statement, when your query returns more than one row. Check your where clause, and make the necessary changes in order to ensure just 1 row is returned. There is a predefined exception for that error. It is: too_many_rows. If you know your query could return more than 1 row in some cases, you should put an exception handler, something like this:
<pre>Begin
SELECT xx into l_xx
FROM table_x;
Exception
when too_many_rows then
' do something
End;</pre>
select distinct oowncode,stkcode
from compexist
where firmnumber = 'FGSB-00001'
and stkcode in (select stkcode
from (select distinct stkcode, oowncode
from compexist
where firmnumber = 'FGSB-00001'
and exchange = 'BSE ')
group by stkcode
having count(*) > 1)
[Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Nse Bill Data Generation cannot take place. ~-1422~ORA-01422: exact fetch returns more than requested number of rows~ORA-06512: at "LDBO.PK_NSEBI
Connectivity error: [Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Nse Bill Data Generation cannot take place. ~-1422~ORA-01422: exact fetch returns more than requested number of rows~ORA-0651
duplicacy of oowncode in accountaddressdetails
SELECT COUNT(*) INTO LNTOTALRECORDS FROM ACCOUNTADDRESSDETAIL ACCOUNTADDRESSDETAIL
WHERE ACCOUNTADDRESSDETAIL.FIRMNUMBER=ICFIRMNUMBER AND ACCOUNTADDRESSDETAIL.OOWNCODE=CLEXTRA.OOWNCODE ;
<pre>Begin
SELECT xx into l_xx
FROM table_x;
Exception
when too_many_rows then
' do something
End;</pre>
select distinct oowncode,stkcode
from compexist
where firmnumber = 'FGSB-00001'
and stkcode in (select stkcode
from (select distinct stkcode, oowncode
from compexist
where firmnumber = 'FGSB-00001'
and exchange = 'BSE ')
group by stkcode
having count(*) > 1)
[Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Nse Bill Data Generation cannot take place. ~-1422~ORA-01422: exact fetch returns more than requested number of rows~ORA-06512: at "LDBO.PK_NSEBI
Connectivity error: [Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Nse Bill Data Generation cannot take place. ~-1422~ORA-01422: exact fetch returns more than requested number of rows~ORA-0651
duplicacy of oowncode in accountaddressdetails
SELECT COUNT(*) INTO LNTOTALRECORDS FROM ACCOUNTADDRESSDETAIL ACCOUNTADDRESSDETAIL
WHERE ACCOUNTADDRESSDETAIL.FIRMNUMBER=ICFIRMNUMBER AND ACCOUNTADDRESSDETAIL.OOWNCODE=CLEXTRA.OOWNCODE ;
Nse Bill Data Generation cannot take place. ~-1422~ORA-01422 exact fetch returns more than requested number of rows~ORA-06512 at LDBO.PK_NSEBI
[Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Nse Bill Data Generation cannot take place. ~-1422~ORA-01422: exact fetch returns more than requested number of rows~ORA-06512: at "LDBO.PK_NSEBI
Connectivity error: [Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Nse Bill Data Generation cannot take place. ~-1422~ORA-01422: exact fetch returns more than requested number of rows~ORA-0651
SPLOGIN IS PRESENT IN LDBO AND SYS USER
duplicacy of oowncode in accountaddressdetails
SELECT COUNT(*) INTO LNTOTALRECORDS FROM ACCOUNTADDRESSDETAIL ACCOUNTADDRESSDETAIL
WHERE ACCOUNTADDRESSDETAIL.FIRMNUMBER=ICFIRMNUMBER AND ACCOUNTADDRESSDETAIL.OOWNCODE=CLEXTRA.OOWNCODE ;
primary key is from
FIRMNUMBER
CODE
but can be dupicate oowncode
Connectivity error: [Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Nse Bill Data Generation cannot take place. ~-1422~ORA-01422: exact fetch returns more than requested number of rows~ORA-0651
SPLOGIN IS PRESENT IN LDBO AND SYS USER
duplicacy of oowncode in accountaddressdetails
SELECT COUNT(*) INTO LNTOTALRECORDS FROM ACCOUNTADDRESSDETAIL ACCOUNTADDRESSDETAIL
WHERE ACCOUNTADDRESSDETAIL.FIRMNUMBER=ICFIRMNUMBER AND ACCOUNTADDRESSDETAIL.OOWNCODE=CLEXTRA.OOWNCODE ;
primary key is from
FIRMNUMBER
CODE
but can be dupicate oowncode
LD file import- in temp file is generating in GBs
there is very much records in tables.
All records are coming.
plz delete the rows and reimport
All records are coming.
plz delete the rows and reimport
Thursday, May 3, 2012
Foxpro Error Error building key for index Operation is invalid for a Memo, Blob, General or Picture field.
Problem :
System Run time Error messages :
Error building key for index
"c:\docume~1\admini~1\locals~1\temp\0000yqe1000z.cdx" tag
"Clrisk".
Operation is invalid for a Memo, Blob, General or Picture
field.
Solution :
Alter system set cursor_sharing=exact scope=both ;
Foxpro Error: Operation is invalid for a Memo, Blob, General or Picture field.
Error: Operation is invalid for a Memo, Blob, General or Picture field
Message: Foxcode table not found, is not correct version or is incompatible.
METHOD: beforeopentables
PROGRAM: frmCheckerCreateUser
There may be following reasons for above error
1) An INDEX command cannot specify a Memo or Blob field as its key expression.
2) There was not enough memory (shared pool) for Visual FoxPro to complete an operation.
3) Unions between differing column types are not allowed when one of the columns is of Memo or General type unless UNION ALL is used.
4) Visual FoxPro cannot update the specified cursor because it is read-only. This can occur when attempting to write to a file created or accessed for read-only purposes.
Solution;
CURSOR_SHARING (Default value: Exact): Share the plan only if text of SQL matches exactly with the text of SQL lying in shared pool.
Sqlplus>show parameter cursor_sharing
Exact is the default value for cursor_sharing.
Sqlplus>ALTER SYSTEM SET cursor_sharing='EXACT';
-- verify default value of EXACT
Sqlplus>show parameter cursor_sharing
-- clear all cached SQL statements
Sqlplus>ALTER SYSTEM FLUSH SHARED_POOL;
Sqlplus>ALTER SYSTEM FLUSH SHARED_POOL;
Friday, April 8, 2011
Oracle error 14402 : ORA-14402: updating partition KEY COLUMN would cause a partition CHANGE
The above error was caused because when you updated the record, it now belongs to a different partition but since row movement between partitions is not enabled on the table, you got that error.
It's easy to solve this problem. Just enable row movement on the table by executing the following command. You need to be logged in as the owner schema of that table or have enough privileges to do so.
ALTER TABLE enable row movement;
It's easy to solve this problem. Just enable row movement on the table by executing the following command. You need to be logged in as the owner schema of that table or have enough privileges to do so.
ALTER TABLE
Primary key Constraints Enable
SQL> alter table CLJOBB disable constraint CLJOBB;
associated index (CLJOBB) will be dropped automatically.
SQL> alter table CLJOBB enable constraint CLJOBB;
alter table CLJOBB enable constraint CLJOBB
*
ERROR at line 1:
ORA-02437: cannot validate (LDBO.CLJOBB) - primary key violated
Enabling of the PK constraint requires association with index.
If we now try to enable the PK constraint again, it will pick up the first index it found on that column and will get associated with it. In case there is no index to get associated, oracle will create a new index with the name same as that of PK constraint.
CREATE UNIQUE INDEX "LDBO"."CLJOBB" ON "LDBO"."CLJOBB" ("FIRMNUMBER", "NFINANCIALYEAR", "CODE", "EXCHANGE", "BOOKCODE", "DVALIDUPTO", "NPRODUCTCODE") PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 104857600 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "INDX" ;
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
CREATE INDEX "LDBO"."CLJOBB" ON "LDBO"."CLJOBB" ("FIRMNUMBER", "NFINANCIALYEAR", "CODE", "EXCHANGE", "BOOKCODE", "DVALIDUPTO", "NPRODUCTCODE") PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 104857600 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "INDX" ;
SQL> alter table CLJOBB enable constraint CLJOBB;
alter table CLJOBB enable constraint CLJOBB
*
ERROR at line 1:
ORA-02437: cannot validate (LDBO.CLJOBB) - primary key violated
SQL> alter table CLJOBB MODIFY CONSTRAINTS CLJOBB ENABLE noVALIDATE;
Table altered.
SQL>
alter table CLJOBB enable VALIDATE primary key;
ERROR at line 1:
ORA-02437: cannot validate (LDBO.CLJOBB) - primary key violated
Cause: attempted to validate a primary key with duplicate values or null values.
Action: remove the duplicates and null values before enabling a primary key.
-----------Primary Key- Firmnumber,Nfinancialyear,Code,Exchange,Bookcode,Dvalidupto,Nproductcode-----
Select A.Firmnumber, A.Nfinancialyear, A.Code, A.Exchange, A.Bookcode, A.Dvalidupto, A.Nproductcode From Cljobb A
Where Rowid > ( Select Min(Rowid) From Cljobb B
Where A.Firmnumber=B.Firmnumber And A.Nfinancialyear=B.Nfinancialyear And A.Code=B.Code And A.Exchange=B.Exchange
and A.Bookcode=b.Bookcode and a.Dvalidupto=b.Dvalidupto and A.Nproductcode=b.Nproductcode
);
associated index (CLJOBB) will be dropped automatically.
SQL> alter table CLJOBB enable constraint CLJOBB;
alter table CLJOBB enable constraint CLJOBB
*
ERROR at line 1:
ORA-02437: cannot validate (LDBO.CLJOBB) - primary key violated
Enabling of the PK constraint requires association with index.
If we now try to enable the PK constraint again, it will pick up the first index it found on that column and will get associated with it. In case there is no index to get associated, oracle will create a new index with the name same as that of PK constraint.
CREATE UNIQUE INDEX "LDBO"."CLJOBB" ON "LDBO"."CLJOBB" ("FIRMNUMBER", "NFINANCIALYEAR", "CODE", "EXCHANGE", "BOOKCODE", "DVALIDUPTO", "NPRODUCTCODE") PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 104857600 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "INDX" ;
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
CREATE INDEX "LDBO"."CLJOBB" ON "LDBO"."CLJOBB" ("FIRMNUMBER", "NFINANCIALYEAR", "CODE", "EXCHANGE", "BOOKCODE", "DVALIDUPTO", "NPRODUCTCODE") PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 104857600 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "INDX" ;
SQL> alter table CLJOBB enable constraint CLJOBB;
alter table CLJOBB enable constraint CLJOBB
*
ERROR at line 1:
ORA-02437: cannot validate (LDBO.CLJOBB) - primary key violated
SQL> alter table CLJOBB MODIFY CONSTRAINTS CLJOBB ENABLE noVALIDATE;
Table altered.
SQL>
alter table CLJOBB enable VALIDATE primary key;
ERROR at line 1:
ORA-02437: cannot validate (LDBO.CLJOBB) - primary key violated
Cause: attempted to validate a primary key with duplicate values or null values.
Action: remove the duplicates and null values before enabling a primary key.
-----------Primary Key- Firmnumber,Nfinancialyear,Code,Exchange,Bookcode,Dvalidupto,Nproductcode-----
Select A.Firmnumber, A.Nfinancialyear, A.Code, A.Exchange, A.Bookcode, A.Dvalidupto, A.Nproductcode From Cljobb A
Where Rowid > ( Select Min(Rowid) From Cljobb B
Where A.Firmnumber=B.Firmnumber And A.Nfinancialyear=B.Nfinancialyear And A.Code=B.Code And A.Exchange=B.Exchange
and A.Bookcode=b.Bookcode and a.Dvalidupto=b.Dvalidupto and A.Nproductcode=b.Nproductcode
);
Labels:
Constraints,
LD Error
Wednesday, April 6, 2011
Constraint stats ORA-02298
Alter table CEXIST DISABLE constraint CEXISTBROKBOOK;
alter table CEXIST disable constraint CEXISTBOOK;
alter table CEXIST ENABLE constraint CK_COMPANYCATEGORY
alter table CEXIST ENABLE constraint CEXISTPRIMARY ;
alter table CEXIST ENABLE constraint COMPANYEXIST ;
SQL> alter table CEXIST ENABLE constraint CEXISTBOOK ;
alter table CEXIST ENABLE constraint CEXISTBOOK
*
ERROR at line 1:
ORA-02298: cannot validate (LDBO.CEXISTBOOK) - parent keys not found
alter table CEXIST MODIFY CONSTRAINTS CEXISTBOOK ENABLE VALIDATE;
ERROR at line 1:
ORA-02298: cannot validate (LDBO.CEXISTBOOK) - parent keys not found
alter table CEXIST MODIFY CONSTRAINTS CEXISTBOOK ENABLE NOVALIDATE;
Constraint stats
Here are the four type of constraint stats. These four constraint stats are applicable for all type of constraints(primary key, foreign key, check etc).
1. ENABLE VALIDATE
2. ENABLE NOVALIDATE
3. DISABLE VALIDATE
4. DISABLE NOVALIDATE
ENABLE VALIDATE is same as ENABLE. Constraint validate the data as soon as we entered in the table.
ENABLE NOVALIDATE is not same as ENABLE. Constraint validates the new data or modified data. It would not validate the existing data in table.
DISABLE NOVALIDATE is the same as DISABLE. The constraint is not checked so data may violate the constraint.
DISABLE VALIDATE means the constraint is not checked but disallows any modification of the constrained columns.
Note : Couple of things needs to be noted down here.
1. Converting NOVALIDATE constraint to VALIDATE would take longer time, depends on how big the data in the table. Although conversion in the other direction is not an issue
2. Disabling primary key constraint will drop the index associated with primary key. Again, when we enable the primary key constraint, it will create the index on the primary key column.
What is the ideal place to use ENABLE NOVALIDATE option?
In a busy environment, some one disabled the constraint accidently or intentionally, and we have already bad data in that table. Now business requested you to load the new set of data, but business wanted to make sure that new set of data should be validated during the load. At this circumstances, we can use ENABLE NOVALIDATE option. This option will validate the new data and old data will not be validated.
What is the ideal place to use DISABLE VALIDATE option?
We disabled the constraint for some reason. We do not want to load any data until we fix the issue and enable the constraint. We can use DISABLE VALIDATE option here. This option would not let you load any data when the constraint is disabled.
alter table CEXIST disable constraint CEXISTBOOK;
alter table CEXIST ENABLE constraint CK_COMPANYCATEGORY
alter table CEXIST ENABLE constraint CEXISTPRIMARY ;
alter table CEXIST ENABLE constraint COMPANYEXIST ;
SQL> alter table CEXIST ENABLE constraint CEXISTBOOK ;
alter table CEXIST ENABLE constraint CEXISTBOOK
*
ERROR at line 1:
ORA-02298: cannot validate (LDBO.CEXISTBOOK) - parent keys not found
alter table CEXIST MODIFY CONSTRAINTS CEXISTBOOK ENABLE VALIDATE;
ERROR at line 1:
ORA-02298: cannot validate (LDBO.CEXISTBOOK) - parent keys not found
alter table CEXIST MODIFY CONSTRAINTS CEXISTBOOK ENABLE NOVALIDATE;
Constraint stats
Here are the four type of constraint stats. These four constraint stats are applicable for all type of constraints(primary key, foreign key, check etc).
1. ENABLE VALIDATE
2. ENABLE NOVALIDATE
3. DISABLE VALIDATE
4. DISABLE NOVALIDATE
ENABLE VALIDATE is same as ENABLE. Constraint validate the data as soon as we entered in the table.
ENABLE NOVALIDATE is not same as ENABLE. Constraint validates the new data or modified data. It would not validate the existing data in table.
DISABLE NOVALIDATE is the same as DISABLE. The constraint is not checked so data may violate the constraint.
DISABLE VALIDATE means the constraint is not checked but disallows any modification of the constrained columns.
Note : Couple of things needs to be noted down here.
1. Converting NOVALIDATE constraint to VALIDATE would take longer time, depends on how big the data in the table. Although conversion in the other direction is not an issue
2. Disabling primary key constraint will drop the index associated with primary key. Again, when we enable the primary key constraint, it will create the index on the primary key column.
What is the ideal place to use ENABLE NOVALIDATE option?
In a busy environment, some one disabled the constraint accidently or intentionally, and we have already bad data in that table. Now business requested you to load the new set of data, but business wanted to make sure that new set of data should be validated during the load. At this circumstances, we can use ENABLE NOVALIDATE option. This option will validate the new data and old data will not be validated.
What is the ideal place to use DISABLE VALIDATE option?
We disabled the constraint for some reason. We do not want to load any data until we fix the issue and enable the constraint. We can use DISABLE VALIDATE option here. This option would not let you load any data when the constraint is disabled.
Labels:
Constraints,
error,
LD Error,
THEORY
Monday, April 4, 2011
LD duplicate transaction number at time of billing
LD duplicate transaction number at time of billing
[Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Bill Financial Posting cannot be Run. ~-1~ORA-00001: unique constraint (LDBO.PK_BILLPROCPRIM) violated~ ORA-06512: at "LDBO.SP_CASHJOBFINPOST", li
Ask Bill Prefix at time of Bill posting
Auto N/NN/060/
Manual N/NN/060-
[Microsoft][ODBC driver for Oracle][Oracle]ORA-20014: Bill Financial Posting cannot be Run. ~-1~ORA-00001: unique constraint (LDBO.PK_BILLPROCPRIM) violated~ ORA-06512: at "LDBO.SP_CASHJOBFINPOST", li
Ask Bill Prefix at time of Bill posting
Auto N/NN/060/
Manual N/NN/060-
LD ASP YEAR END PROCESS FY 1112
LD ASP YEAR END PROCESS FY 1112
Before processing for New Year financial process for ASP. We have to log into the local LD and follow the following link-
o General Utilities-> General Utilities->Wan Enable
o Select Firm, select the New Financial Year, Tick on Wan Enable & click on save button.
o User has to do for all firm for which New Financial Year has to be change.
These are following points which have to be done for the New Year financial Process for ASP
o Click Start->Run->CMD
1) Stop the IIS Server by typing the following command – iisreset/stop
o Click on the Control Panel -> Administrative Tools-> Component Services-> Select all components-> Right click and select Shut Down.
o Copy the following files from m:\LD\sysuser folder system.*, setup.*, esetup.*, excode.*, directory.* ,firm.* to asp server i.e. (d:\LD\sysuser)
o After copying the file Go to Fox Pro write the following command
Set excl off
use d:/ld/sysuser/directry.DBF
Brow Change the Data_Drive (i.e. Drive letter for ld server) Change the Lwanenable =”T” (for the new firm if it is not been viewed at Branch level.)
Clos all
o Go to cmd -> type the following command – iisreset/start
If there is problem in Pre-Printed file then do the following Points
o Go Visual Foxpro and type the following text
Set excl off
Rest from m:\(firmfolder)\ldvar.mem
Display memo
_LDDDRIVE = ‘D:’ (Where the ld is stored on LD Server)
_LDDRIVE = ‘D:’ (Where the ld is stored on LD Server
Save all like *.* to m:\(firmfolder)\ldvar.mem
Clea
Close all
------------------------------
ARI1112SRV =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.84)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ari1112)
)
)
---------------------------------------------
Issue
ROLES TO GRANTED CONTAIN EXTRA PRIVILEGES
REASON:BRANCH HAVE STANDARD VERSION
------revoke_std_ver.sql
revoke insert,update on TBLUSERPROFILES from Remoteuser ;
revoke insert,update on TBLUSERPROFILES from firmpermission ;
create role userprofiles ;
grant insert,update on TBLUSERPROFILES to userprofiles ;
revoke execute on SP_ASIANEFFBAL from FIRMPERMISSION;
revoke insert on TBLFIRMCREATION from FIRMPERMISSION ;
revoke insert,update,delete on TBLMAILERDETAIL from FIRMPERMISSION ;
revoke execute on SP_FIRMCREATION from FIRMPERMISSION;
revoke execute on PK_JOURNALIMPORT from Remoteuser ;
revoke execute on PK_JOURNAL from remoteuser ;
revoke execute on ldbo.SP_LIENFUNDTRANSFER from Remoteuser ;
revoke insert on TBLBILLTAGGING from cashbankadd ;
REVOKE UPDATE ON ESETTLE FROM CASHBANKADD;
ROLE_ROLE_PRIVS
ROLE_SYS_PRIVS
ROLE_TAB_PRIVS
USER_COL_PRIVS
USER_COL_PRIVS_MADE
USER_COL_PRIVS_RECD
USER_ROLE_PRIVS
USER_SYS_PRIVS
USER_TAB_PRIVS
USER_TAB_PRIVS_MADE
USER_TAB_PRIVS_RECD
Before processing for New Year financial process for ASP. We have to log into the local LD and follow the following link-
o General Utilities-> General Utilities->Wan Enable
o Select Firm, select the New Financial Year, Tick on Wan Enable & click on save button.
o User has to do for all firm for which New Financial Year has to be change.
These are following points which have to be done for the New Year financial Process for ASP
o Click Start->Run->CMD
1) Stop the IIS Server by typing the following command – iisreset/stop
o Click on the Control Panel -> Administrative Tools-> Component Services-> Select all components-> Right click and select Shut Down.
o Copy the following files from m:\LD\sysuser folder system.*, setup.*, esetup.*, excode.*, directory.* ,firm.* to asp server i.e. (d:\LD\sysuser)
o After copying the file Go to Fox Pro write the following command
Set excl off
use d:/ld/sysuser/directry.DBF
Brow Change the Data_Drive (i.e. Drive letter for ld server) Change the Lwanenable =”T” (for the new firm if it is not been viewed at Branch level.)
Clos all
o Go to cmd -> type the following command – iisreset/start
If there is problem in Pre-Printed file then do the following Points
o Go Visual Foxpro and type the following text
Set excl off
Rest from m:\(firmfolder)\ldvar.mem
Display memo
_LDDDRIVE = ‘D:’ (Where the ld is stored on LD Server)
_LDDRIVE = ‘D:’ (Where the ld is stored on LD Server
Save all like *.* to m:\(firmfolder)\ldvar.mem
Clea
Close all
------------------------------
ARI1112SRV =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.84)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ari1112)
)
)
---------------------------------------------
Issue
ROLES TO GRANTED CONTAIN EXTRA PRIVILEGES
REASON:BRANCH HAVE STANDARD VERSION
------revoke_std_ver.sql
revoke insert,update on TBLUSERPROFILES from Remoteuser ;
revoke insert,update on TBLUSERPROFILES from firmpermission ;
create role userprofiles ;
grant insert,update on TBLUSERPROFILES to userprofiles ;
revoke execute on SP_ASIANEFFBAL from FIRMPERMISSION;
revoke insert on TBLFIRMCREATION from FIRMPERMISSION ;
revoke insert,update,delete on TBLMAILERDETAIL from FIRMPERMISSION ;
revoke execute on SP_FIRMCREATION from FIRMPERMISSION;
revoke execute on PK_JOURNALIMPORT from Remoteuser ;
revoke execute on PK_JOURNAL from remoteuser ;
revoke execute on ldbo.SP_LIENFUNDTRANSFER from Remoteuser ;
revoke insert on TBLBILLTAGGING from cashbankadd ;
REVOKE UPDATE ON ESETTLE FROM CASHBANKADD;
ROLE_ROLE_PRIVS
ROLE_SYS_PRIVS
ROLE_TAB_PRIVS
USER_COL_PRIVS
USER_COL_PRIVS_MADE
USER_COL_PRIVS_RECD
USER_ROLE_PRIVS
USER_SYS_PRIVS
USER_TAB_PRIVS
USER_TAB_PRIVS_MADE
USER_TAB_PRIVS_RECD
LD CLIENTLEVEL YEP1112
Create Role ClientPassEdit ;
Grant update on Accountemaildetail to ClientPassEdit ;
Grant clientpassedit to cllvl;
OTHERWISE
make entry in tnsnames.ora otherwise ECN is not be accessible from clientlevel
DIG1112SRV =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.84)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ARI1112)
)
)
Grant update on Accountemaildetail to ClientPassEdit ;
Grant clientpassedit to cllvl;
OTHERWISE
Technical Information (for support personnel)
- Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC driver for Oracle][Oracle]ORA-01031: insufficient privileges
/clientlevel/clientaccess/default.asp, line 257 - Browser Type:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) - Page:
POST 334 bytes to /clientlevel/clientaccess/default.asp
make entry in tnsnames.ora otherwise ECN is not be accessible from clientlevel
DIG1112SRV =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.84)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ARI1112)
)
)
LD network.dbf error at time of FnO sauda file import
LD network.dbf error at time of FnO sauda file import
SQL> drop sequence Sq_Scripuniquenumber ;
Sequence dropped.
SQL> SELECT MAX(CODE) FROM COMPANY ;
MAX(CODE)
----------
Co-0054502
SQL> Create Sequence Sq_Scripuniquenumber minvalue 54503 maxvalue 9999999 ;
Sequence created.
SQL> drop sequence Sq_Scripuniquenumber ;
Sequence dropped.
SQL> SELECT MAX(CODE) FROM COMPANY ;
MAX(CODE)
----------
Co-0054502
SQL> Create Sequence Sq_Scripuniquenumber minvalue 54503 maxvalue 9999999 ;
Sequence created.
Sunday, April 3, 2011
ORA-00600: internal error code
ORA-00600: internal error code, arguments: [15735], [2244], [2152], [], [], [], [], []
solution:
alter system set parallel_execution_message_size=4096 scope=spfile;
shut immediate
startup
On most platforms, the default value is 2148 bytes if parallel_automatic_tuning is set to FALSE, and 4096 bytes if parallel_automatic_tuning = TRUE. The default value is adequate for most applications. Larger values require a larger shared pool. Larger values result in better performance at the cost of higher memory use. For this reason, replication gets no benefit from increasing the size.
When parallel_automatic_tuning = TRUE, message buffers are allocated out of the large pool. In this case, the default is generally higher.
solution:
alter system set parallel_execution_message_size=4096 scope=spfile;
shut immediate
startup
On most platforms, the default value is 2148 bytes if parallel_automatic_tuning is set to FALSE, and 4096 bytes if parallel_automatic_tuning = TRUE. The default value is adequate for most applications. Larger values require a larger shared pool. Larger values result in better performance at the cost of higher memory use. For this reason, replication gets no benefit from increasing the size.
When parallel_automatic_tuning = TRUE, message buffers are allocated out of the large pool. In this case, the default is generally higher.
Subscribe to:
Posts (Atom)