Saturday, 4 February 2023

Real time issue schema MAD refresh

Real time issue  schema MAD refresh

================================================

application is not working after the refresh due to the sequence issues.
When the application tries to insert a new record, data integrity violation is thrown due to the id generated from the sequence


===========================================================================

1> first check the production sqquance numbers 

select max(id) from mad_service_mapping ;
-- 
returns 953543


Test database  


select sequence_service_mapping.nextval from dual; 
--returns 953536

So

from the above  output there is mismatch in sequances 

steps to resolve the issue




step 1 first login production database and exicute the below command to get the ddl of sequances 

ddl extraction  sequaqnces 




select dbms_metadata.get_ddl('SEQUENCE', sequence_name, sequence_owner)
from dba_sequences where sequence_owner = 'MAD’;

save create statements to file

==================================



Drop the sequances in test database ....

MADT2 
 
and exicute the create statement which is taken the from production in the step 1 

afer creation the sequances in test database....so problem resolved application is working  Fine



second senarion in dev database .....OPSD2 ..


Dev databases are completly are down due to the filel system /ora is filled 100 % ....


check  the file system status /ora 
[oraprod@corracc201p 
alert]$ df -h .
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda7             2.0G  2.0G  0     100% /ora





If you face such issue.
we can remve the trace files which are in the bdump location below is command to remove the old trace files 



find *.trc -mtime +10| xargs rm 


















0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home