gReetings!
I just need to throw this out there and see if anyone seconds it... I have
a server up until last week all it had/did was store the db files that
everyone uses. Last week my network admin made this server a back up domain
controler due to a failing 5+ year old, main server which does everything
for this network and he wanted a back up just incase it completely goes
down. Well last thursday I had table not increment the Initial Value to
next value after an insert and again yesterday I had the same thing happen
to a different table. (btw, I've had this issue a few times previously when
the files resided on the main server but not since the transfer to this new
server) So I'm thinking there is something with this server being a domain
control and handling the db but my net admin insists it shouldn't be an
issue. My thought is, if weirdness starts happening, first I look for is
what is different now compared to before, in this case it's the addition of
a back up domain controler. OH and last Monday the db got corrupted but I'm
thinking that was the result of the faulty main server. Using RScope I was
able to do some pretty intense repairing and was then able to restore it to
a point that I could unload all the data but here is what a table looked
like after using rscope to fix column names that appear as | in rscope....
CREATE TABLE `CustInsurance` CASCADE +
(`CustInsuranceID` INTEGER NOT NULL +
('Value for column CustInsuranceID cannot be null') , +
`CID` INTEGER , +
`CustInsStatus` TEXT (1) DEFAULT 'A' , +
`CustInsType` TEXT (1) DEFAULT '2' , +
`CustInsurOrder` TEXT (1) NOT NULL +
('Please select the priority order.') , +
`InsCID` INTEGER NOT NULL +
('Please select an Insurance / Payor') , +
`InsBillCAID` INTEGER NOT NULL +
('Please select the billing address.') , +
`InsPACAID` INTEGER NOT NULL +
('Please select the PA address.') , +
`PolicyGroupName` TEXT (60) , +
`PolicyNo` TEXT (29) , +
`GroupNoIDCode` TEXT (2) DEFAULT '1W' , +
`GroupNo` TEXT (29) DEFAULT USER , +
`InsurVerifiedDate X_SIZE` DATE DEFAULT USER , +
`CustInsNote FACTOR` NOTE (4000) DEFAULT USER , +
`EnteredBy FACTOR` INTEGER DEFAULT USER , +
`EnterDate IDX` DATE DEFAULT USER , +
`UpdatedBy ARY_KEY` INTEGER DEFAULT USER , +
`UpdatedDate UE_INDEX` DATE DEFAULT USER )
and here is how it should be...
CREATE TABLE `CustInsurance` CASCADE +
(`CustInsuranceID` INTEGER NOT NULL +
('Value for column CustInsuranceID cannot be null') , +
`CID` INTEGER , +
`CustInsStatus` TEXT (1) DEFAULT 'A' , +
`CustInsType` TEXT (1) DEFAULT '2' , +
`CustInsurOrder` TEXT (1) NOT NULL +
('Please select the priority order.') , +
`InsCID` INTEGER NOT NULL +
('Please select an Insurance / Payor') , +
`InsBillCAID` INTEGER NOT NULL +
('Please select the billing address.') , +
`InsPACAID` INTEGER NOT NULL +
('Please select the PA address.') , +
`PolicyGroupName` TEXT (60) , +
`PolicyNo` TEXT (29) , +
`GroupNoIDCode` TEXT (2) DEFAULT '1W' , +
`GroupNo` TEXT (29) , +
`InsurVerifiedDate` DATE , +
`CustInsNote` NOTE (4000) , +
`EnteredBy` INTEGER , +
`EnterDate` DATE , +
`UpdatedBy` INTEGER , +
`UpdatedDate` DATE )
notice these columns in the bad table structure...
`GroupNo` TEXT (29) DEFAULT USER , +
`InsurVerifiedDate X_SIZE` DATE DEFAULT USER , +
`CustInsNote FACTOR` NOTE (4000) DEFAULT USER , +
`EnteredBy FACTOR` INTEGER DEFAULT USER , +
`EnterDate IDX` DATE DEFAULT USER , +
`UpdatedBy ARY_KEY` INTEGER DEFAULT USER , +
`UpdatedDate UE_INDEX` DATE DEFAULT USER )
no matter what I did I couldn't get the columns to not have the data after
the long series of spaces or the DEFAULT USER which makes me think there was
a change in a network user at the same time this got corrupted anyone else
have any thoughts?
So I was able to get this back to good last Monday and can't find any issues
with the db since...until autonumbers decide to not increment and I still
think it's the addition to db server of the back domain controler for the
autonumber issue.
Thanks Everyone!
PS. My net admin after alittle struggle has removed the back domain
controler funtions from that server so hopefully I don't see this issue
again.
