Hi All,

one of my customers has discovered a problem with EBU 2.2 which may be relevant 
to you.  He is using the old ADSM agent for Oracle code with EBU 2.2.0.6, ADSM 
3.1.2.50 and Oracle 7.3.3.4 under AIX.

Unix guys may be aware that the Unix timestamp went to 10 digits earlier this 
month.  EBU saves its files with a generated filename of 
<sequencenumber><timestamp>.  It seems that the backup process copes fine with 
the longer timestamp, and so the file is properly saved, however, the restore 
process only takes the first 9 digits of the timestamp and hence the file can't 
be found in ADSM. This showed up in a restore of an archive log.

I'd suggest that anyone using EBU gives this a try to ensure that they are not 
exposed.

Steve Harris
AIX and ADSM Contractor, Brisbane Australia


 




**********************************************************************
This e-mail, including any attachments sent with it, is confidential 
and for the sole use of the intended recipient(s). This confidentiality 
is not waived or lost if you receive it and you are not the intended 
recipient(s), or if it is transmitted/ received in error.  

Any unauthorised use, alteration, disclosure, distribution or review 
of this e-mail is prohibited.  It may be subject to a statutory duty of 
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this 
e-mail in error, you are asked to immediately notify the sender by 
telephone or by return e-mail.  You should also delete this e-mail 
message and destroy any hard copies produced.
**********************************************************************